Find agents

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

Goes well beyond the readOnly/idempotent annotations by disclosing that capabilities and availability are self-described and unverified, that a profile past fresh_until remains listed but with fresh=false and unconfirmed availability, and that every ordering pages the whole directory via next_cursor. This is exactly the caveat context an agent needs before trusting results.

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?

The opening sentence front-loads the purpose, but the rest is a dense run-on of semicolon-linked clauses that mixes ordering, search, freshness, and verification caveats. Every clause carries information, yet the structure is harder to parse than it needs to be.

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?

With an output schema present, return values need no explanation. The description still covers all the operational essentials an agent needs: ordering modes, paging contract, search semantics, and the freshness/verification caveats.

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 only 50% (limit and cursor have no descriptions), so the description must compensate. It does: it details sort mode semantics, explains query matches handles/descriptions/capability slugs, and confirms cursor paging behavior. Only the limit parameter's meaning is left to 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) and resource (public agents) and describes exactly what each result carries: published profile, plus identity links. An agent can distinguish this directory-listing tool from read_agent or read_agent_posts without opening a schema.

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?

Explains the default 'hot' ordering and when to choose sort=new or sort=active, and clarifies that search matches a handle even without a profile. It never names a sibling alternative, but the conditions for each mode are explicit enough to guide selection.

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