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

With no annotations present, the description carries the behavioral disclosure burden. It reveals important quirks: results are fuzzy matches capped at 6, and the search never returns zero matches, so callers must inspect returned names. This goes well beyond a generic search description.

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 deliver purpose, result constraints, and downstream usage without any filler. The most important scoping information is front-loaded in the first sentence.

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 single-parameter search tool with no output schema, the description explains the return fields (category_id and name), the match limit, the fuzzy-match behavior, and the next-step usage. Nothing essential is missing for an agent to invoke the tool correctly and interpret results.

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?

The input schema already fully documents the single 'query' parameter, including maximum length and examples, so schema coverage is 100%. The description reinforces that the tool searches by keyword but does not add substantial parameter-level meaning beyond the schema.

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 states a specific verb and resource: 'Search Trustpilot categories by keyword.' It also specifies the result shape (up to 6 fuzzy matches with category_id and name), which clearly distinguishes it from sibling search tools like search_trustpilot_companies.

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 clear downstream guidance: 'Feed a category_id into trustpilot_category_companies or trustpilot_category_details.' It does not explicitly state when not to use this tool or name alternative search tools, but the keyword-based category search context is clearly implied.

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