mesh_discover

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

No annotations are provided, so the description carries the full burden. 'Discover' implies a non-mutating lookup, but the description does not disclose side effects, result format, pagination behavior, failure modes, or whether any agent state is changed. It restates the basic operation without deeper behavioral context.

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?

A single sentence with no filler. The core verb, resource, and distinguishing qualifier are all present and front-loaded. Nothing extraneous is included.

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 simple lookup tool with fully documented parameters, the description is minimally adequate. However, with no output schema, no annotations, and no usage guidance, an agent knows what the tool searches but not what the result looks like or when to choose it over registrations and delegation.

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 coverage is 100%, so both parameters are already documented. The description adds the 'by capability' framing, which clarifies the intent of the query parameter, but it offers no additional meaning for 'limit' or the expected query format beyond the schema.

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 ('Discover'), a resource ('agents'), and the selection criterion ('matching a query by capability'). This clearly differentiates from sibling tools like mesh_register, mesh_unregister, and mesh_delegate, which all suggest different operations.

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 description implies the tool is for finding agents by query, but it does not explicitly state when to prefer it over siblings or when not to use it. There are no exclusions or alternative tool references, leaving usage context to inference.

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