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

With no annotations present, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: the cost model ('1 point per returned record'). It still omits ordering, pagination, rate limits, and whether the call requires a valid Trustpilot business to exist, so the safety/cost profile is only partially covered.

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?

A single front-loaded sentence pairs the purpose with the returned fields, and a short second clause states the billing rate. No filler, nothing repeated from the schema, and the most decision-relevant content leads.

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 simple 2-parameter reader with no output schema, the description usefully enumerates the return fields (rating, text, author) and the cost per record, covering what the schema cannot. It stops short of noting ordering/pagination behavior for the up-to-300 item range, which is a minor remaining gap.

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 both parameters (business, max_items) are already fully documented in the schema, including the 300 cap and default of 10. The description's 'by domain or URL' merely restates the schema's business description, adding no new syntax or format detail.

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 gives a specific verb and resource ('Get customer reviews for a Trustpilot business') and enumerates the returned fields (rating, text, author), which clearly separates it from a generic business-lookup tool. It does not, however, name the sibling tools (run_trustpilot, run_trustpilot_search) or explain how it differs from them.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent is left to infer that this is the reviews path and must guess between it, run_trustpilot, and run_trustpilot_search on its own.

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