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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description does add a genuinely useful behavior: the cost model (1 point per returned record). It says nothing about pagination behavior or how max_items interacts with billing, which leaves a real gap for a billed search.

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?

Two tight sentences with no filler, and the resource scope is front-loaded before the cost note. It is appropriately sized, though it could have spent one clause on sibling differentiation instead of restating the returned fields.

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 2-parameter, no-output-schema tool with full annotation coverage and full schema coverage, the description is close to adequate. What it lacks is any routing help against the near-identical sibling Trustpilot tools, which is the main ambiguity an agent faces here.

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 (query, max_items) are already documented with types, bounds and defaults. The description repeats the keyword idea but adds no syntax, format or matching-semantics detail beyond the schema, so baseline 3 applies.

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 (search) and resource (Trustpilot businesses) and enumerates the fields surfaced (name, domain, rating, review count). It does not, however, distinguish itself from the sibling tools run_trustpilot and run_trustpilot_reviews, which an agent scanning this list would likely confuse it with.

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 guidance on when to use this versus run_trustpilot or run_trustpilot_reviews, nor any stated prerequisites or exclusions. The only actionable signal is the implied cost note, which speaks to budget rather than selection.

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