identity__discover_agents

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

Discloses key behaviors: filters to active agents, AND semantic matching, ordering by match count then reputation. Lacks details on pagination or output format, but given no annotations, this is strong.

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?

Single concise sentence with domain prefix and clear functional description. No wasted words.

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?

Covers purpose and key behavioral traits, but lacks output format description and limit semantics. For a simple tool with no output schema, additional context would improve completeness.

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?

Explains capabilities parameter's matching logic, but does not mention the limit parameter. With 0% schema description coverage, the description partially compensates but misses covering the limit parameter.

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?

Description clearly states the tool finds ACTIVE agents matching requested capabilities with AND semantics and deterministic ordering. Distinguishes well from sibling identity tools like resolve_agent and list_registrations.

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?

Implied usage for capability-based discovery, but no explicit when-not or alternatives. Agent might benefit from guidance vs other identity discovery methods.

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