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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the response contents (specs, dated price, score, sub-scores), which is useful, but it does not address behaviors such as not-found handling, name ambiguity, normalization, or whether the operation is purely reads with no side effects.

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?

The description is a single, well-structured sentence that front-loads the return value and then states the input format with examples. Every word earns its place, with no filler or redundancy.

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 one-parameter lookup tool, the description covers the essential invocation details: what to pass, the acceptable input formats, and what data to expect back. It does not detail the exact response shape, and there is no output schema, but the described output fields are sufficient for an agent to use the tool confidently.

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 schema already fully documents the single 'query' parameter, so the baseline is 3. The description adds concrete examples ('Mammotion Luba 2 AWD', 'Segway Navimow i110') and clarifies that name, brand + model, or slug are all acceptable, which helps an agent phrase queries correctly beyond the schema text.

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 uses a specific verb ('Get') and a specific resource ('a single robot lawn mower'), and clearly enumerates what is returned: full specs, dated price, 0-5 score, and sub-scores. The phrase 'by name or slug' with concrete examples makes the purpose unmistakable and distinguishes it from list/compare/recommend siblings.

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 implies when to use the tool by focusing on 'a single robot lawn mower by name or slug', so an agent can infer it is for known-model lookups rather than browsing or comparing. However, it never explicitly names sibling alternatives or states when not to use them, leaving some routing to inference.

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