find_agent

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

No annotations provided, so description carries full burden. Lists return fields (repo/endpoint, GitHub stars, activity, tags) and hints at read-only nature. Does not disclose pagination or ordering behavior, but is generally 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?

Three concise sentences front-loaded with purpose. No wasted words; every sentence adds value.

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 no output schema, description adequately explains return values. Does not mention pagination, sorting, or error conditions, but is complete enough for a search tool with minimal parameters.

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 50% (query described, limit not). Description adds meaning to query ('by capability or task') but does not explain limit beyond the schema. Baseline 3 as schema already covers half; description does not fully compensate for missing limit documentation.

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 verb 'Search', resource 'Beacon registry for open-source AI agents', and scope 'by capability or task' with examples. Clearly distinguishes from sibling tools like agent_details (details) and top_agents (listing).

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?

Provides clear context on when to use (searching for agents by task/ability). Lacks explicit exclusion criteria or when to prefer alternatives, but examples and sibling names imply usage boundaries.

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