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

With no annotations, the description carries the full burden and discloses pagination limits (20 per page, up to 500 pages), the exact fields returned, and the category's size/subcategories. It also enumerates filtering and sorting options, although it does not cover rate limits or error behavior.

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 tightly packed sentences: action/results, filters/sorts, and category ID resolution. No filler, and the most important information is front-loaded.

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 paginated listing endpoint with no output schema, the description explains the returned fields, pagination bounds, filter/sort capabilities, and how to find valid category IDs. This is sufficient for an agent to invoke it 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 coverage is 100%, so parameters are already documented; the description adds value by explaining pagination scope, the filter/sort dimensions, and how to resolve category_id. It complements rather than repeats 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?

States a specific verb and resource ('List the companies in a Trustpilot category') and includes concrete result details (name, domain, TrustScore, review count, categories, location, category size/subcategories). It clearly differentiates from sibling search tools by focusing on category-scoped listing rather than general search.

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 tells the agent how to obtain category IDs (docs or search_trustpilot_categories) and lists applicable filters/sorts, giving clear context for when this listing tool is appropriate. It does not explicitly name sibling alternatives like trustpilot_category_newest, but the category-scoped behavior is unambiguous.

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