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

No annotations are provided, so the description carries the transparency burden. It discloses a key behavioral trait: results are ranked by the 0-5 BestRobotMower Score, highest first, and 'List' implies a read-only operation. It does not mention edge behaviors like empty results or default limit handling, but the schema covers the limit default.

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 sentences, front-loaded with the action and resource, with no filler. The ranking behavior is stated compactly in the second sentence, and every clause earns its place.

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 read-only list tool with 7 optional filters and no output schema, the description covers the core purpose and the result ordering. It does not detail returned model fields or pagination, but the 100% schema coverage and simple list semantics make the description sufficient; a mention of the default/max limit would be a minor improvement.

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 baseline applies. The description names the filter dimensions (brand, navigation, price, lawn area, slope, score) but adds no semantic detail beyond what the parameter descriptions already provide.

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 ('List and filter') and a named resource ('robot lawn mowers in the BestRobotMower.co dataset'), which clearly distinguishes it from get, compare, and recommend siblings. The ranking clause further defines the output as a browse/filter operation rather than a single-item or recommendation tool.

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 conveys the intended use case—listing and filtering a dataset—but it never names sibling tools or states when to prefer them. Usage is implied through 'List and filter' rather than explicitly guided with alternatives or exclusions.

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