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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context beyond those: it is free, it searches a pay-per-call catalog, and it returns pricing in USDC and an example input. This helps the agent understand the tool's role without over-explaining.

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 compact and front-loaded: 'FREE' and the action verb appear first, followed by catalog scope, return value, and usage instruction. Every sentence contributes distinct information with no filler.

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?

For a search/discovery tool with full schema coverage and safety annotations, the description is complete. It tells the agent what the tool searches, what it returns, that it is free, and when to use it. No critical operational detail is missing.

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 schema already documents both parameters (query and max_price_usdc) with examples. The description adds context about the catalog content and result shape but does not add new parameter-level meaning. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Search the SYNTHORA catalog'. It clearly distinguishes this meta-search tool from the many data-provider siblings by stating it returns matching tools with price and example input, and by framing itself as the tool-selection entry point.

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 gives explicit usage direction: 'Use it first to pick the right tool.' It also signals cost context with 'FREE' and describes what the search returns. It does not explicitly state when not to use it, but the 'use first' instruction is strong enough for an agent to know this is the discovery step before invoking a sibling tool.

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