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

No annotations are present, so the description carries the full burden. It discloses that the tool uses AI-powered semantic matching and supports structured filters, but does not describe behavioral aspects such as whether results are scored or ranked, how empty results are handled, or if it is read-only (inferred but not explicit). The description provides adequate but not comprehensive behavioral context.

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 sentences: first states purpose, second gives an example query, third lists alternatives. Every sentence serves a clear role without fluff. Highly efficient and front-loaded with the most important information.

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 9 parameters (all documented in schema) and no output schema, the description provides a solid overview of purpose, usage, and alternatives. However, it omits details about the return format (e.g., list of tools with scores). This is a minor gap for an otherwise well-rounded description.

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%, so the baseline is 3. The description adds value by stating 'Supports structured filters to narrow results (e.g., openSource + deploymentModel)', which implies combinable filters and provides an example. This extra context justifies a score above baseline.

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 'Search for AI tools using natural language with AI-powered semantic matching', identifying the verb (search) and resource (AI tools). It distinguishes from siblings by explicitly naming alternatives for exact/keyword searches (search_listings) and comparisons (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?

The description provides explicit when-to-use guidance ('Best for conceptual queries') and when-not-to-use with specific alternative tools named ('For exact name/keyword searches, use search_listings instead. For comparing specific tools, use compare_listings.'). This leaves no ambiguity about appropriate contexts.

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