find_tools

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

Mentions 'AN Score' ranking (behavioral trait), but lacks disclosure on read-only safety, rate limits, or what AN Score represents. Carries full burden since annotations are absent.

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?

Extremely efficient 7-word description. Front-loaded with action and scope. 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?

Simple 2-parameter tool, but lacks output description (no output schema provided). Could clarify search scope (all servers? current server?) and relationship to 'get_score' sibling given AN Score reference.

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 100% documenting both 'query' and 'limit'. Description doesn't add parameter-specific semantics beyond schema (e.g., query syntax tips, max limit rationale). Baseline 3 appropriate given schema completeness.

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?

Clear specific verb ('Semantic search'), resource ('agent tools'), and ranking criteria ('ranked by AN Score'). Compact but complete purpose statement.

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?

No guidance on when to use this versus sibling 'discover_capabilities' or other discovery tools. No mention of prerequisites or when results are useful.

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