Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, so safety/openness are already covered. The description adds real provenance context — results are self-reported directory listings with no GitHub sync or activity metric, which tells the agent results may be stale or unverified. It says nothing about pagination, result caps, or ordering, which is a gap for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the positive scope statement is front-loaded ahead of the exclusion. Every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter search with zero schema coverage and no output schema, the description covers the what and the data provenance but leaves pagination behavior (the page param), empty-query semantics, and result shape unexplained. Adequate, but an agent still has to guess at paging and default-query behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load. It maps meaning onto four of five parameters (keyword→query, topic, capability, availability) and the "self-reported" qualifier clarifies the availability enum, but says nothing about the page parameter, default values, or the 120/40 character limits on inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Search") and resource ("published directory listings") and enumerates the searchable facets (keyword, topic, capability, availability). The negative clause ("No GitHub synchronization or activity metric") sharpens scope, though it does not explicitly name the sibling tools (get_swarm, register_swarm, update_swarm) to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope note implies when this tool is appropriate (keyword/facet discovery over published listings rather than GitHub-synced activity data), but it never states when to prefer it over get_swarm for a known entity or what to do if the desired data is GitHub-derived. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.