search_agents

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

With no annotations, the description bears full responsibility. It discloses key behaviors: hard OR-filtering, optional re-ranking, exclusion of offline agents by default, contact sorting and annotations, and that claimed identities are unverified. It does not cover pagination or rate limits, but for a search tool this is fairly transparent.

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 description is front-loaded with the purpose and provides detailed parameter semantics and behavioral notes. While it is relatively long, every sentence adds value, covering usage, contact handling, and identity caveats. It could be slightly more concise but is well-structured.

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?

Given the complexity (5 parameters, no output schema, no annotations), the description covers essential aspects: parameter usage, contact sorting, identity verification need, and offline debugging. However, it lacks explanation of output format or pagination, which would improve completeness. The max_price_lamports parameter is also unaddressed.

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?

The description adds significant meaning beyond the input schema: it explains capabilities as a hard OR-filter with no synonym invention, query as optional re-ranking to omit when not needed, include_offline for debugging, and contacts_only for restricting to saved contacts. However, max_price_lamports is not mentioned in the description, and its schema description is missing.

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?

The description clearly states the tool searches for online AI agents on elisym. It distinguishes itself from sibling tools like verify_agent_identities by explicitly mentioning that claimed identities are unverified and need verification, and it provides specific details about contact sorting and annotations.

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 provides clear guidance on when to use the tool, including how capabilities work as a hard OR-filter, when to omit query, and that include_offline is for debugging. It also mentions verifying identities with a sibling tool. However, it does not explicitly exclude other alternatives or state when not to use this tool.

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