Agent Discovery

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered in structured data. The description still adds real value by ruling out side effects explicitly ('never installs or connects') and disclosing the result shape (ranked with relevance scores), which the annotations do not convey.

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 short sentences, no redundancy, with the strongest disambiguating fact (search-only, no install/connect) placed immediately after the purpose statement. Every clause carries information.

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?

An output schema exists, so return-value detail is not required, and the description's brief note about ranked relevance-scored results is sufficient. The only meaningful gap is the absence of any routing guidance relative to the you-search sibling.

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 100%, so every parameter is already documented in the schema (limit bounds, natural-language query, finder enum, optional public finder_url). The description only loosely gestures at this via 'ARD Agent Finder services' and 'ranked results'; no syntax or format detail is added, so baseline 3 applies.

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') with a well-enumerated resource set (AI agents, MCP servers, A2A agents, skills) and names the discovery mechanism (ARD Agent Finder services). It does not, however, distinguish itself from the sibling you-search, leaving the agent to infer which search surface to pick.

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?

'Search-only — never installs or connects' implies a usage boundary (discovery only, no side effects on the user's environment), which is useful. But there is no explicit when-to-use vs. the sibling you-search, and no stated prerequisites or query-phrasing guidance, so usage must be inferred.

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