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

No annotations are provided, so the description carries full burden. It explains the tool returns 'curated, ranked results with explanations' and handles search, filtering, scoring, ranking. No destructive behavior is mentioned; it's presumably read-only. The description could be more specific about output format or rate limits, but overall it's transparent enough.

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 concise and front-loaded with purpose, then provides examples. Every sentence adds value, no wasted words. It is appropriately sized for the tool's complexity.

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, the description explains the general nature of output ('curated, ranked results with explanations'), but lacks specifics on the structure of results (e.g., list of tool objects with scores). However, with only 2 parameters, high schema coverage, and clear examples, it is mostly complete for an AI agent to understand and invoke the tool correctly.

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% (all parameters have descriptions in input schema). The description adds example usage and context but does not add new parameter-level details beyond the schema. Baseline is 3 for high coverage, and the description does not significantly enhance parameter understanding beyond what schema provides.

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 provides 'AI-powered tool recommendations for a specific need' and is 'the recommended starting point'. It distinguishes from siblings by noting it handles search, filtering, scoring, and ranking in one call, and explicitly suggests using it instead of chaining other tools like search_listings + get_listing + compare_listings.

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?

Explicit guidance is given: 'Use this instead of chaining search_listings + get_listing + compare_listings', making it clear when to use this tool vs alternatives. The description also implies usage for natural language queries with specific examples.

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