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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds valuable context by detailing the exact return fields (score range, verdict labels, price range, pros/cons, source URL) and linking to the methodology. This goes beyond the annotations and helps the agent anticipate the tool's output.

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 concise and front-loaded, stating the core function in the first sentence, then providing necessary detail about the metric and returned data. 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?

Given the tool's low complexity (single parameter, no output schema), the description fully covers what the tool returns, including the verdict scale, price range, pros/cons, and source URL. It also provides additional context about the methodology, making it self-contained for an agent.

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 describes the only parameter (product_name) with examples and coverage at 100%. The description does not add new semantics beyond clarifying it targets smart home products, which is already evident; thus a baseline score of 3 is appropriate.

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 clearly states the tool's purpose: to get the SHE Consensus Score and expert verdict for a specific smart home product. It distinguishes itself from sibling tools like search or compare by focusing on retrieving a consensus verdict for a single product.

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 usage when needing a verdict for a specific product, but it does not explicitly compare with alternatives or state when not to use it. No exclusionary guidance is provided, leaving the agent to infer from the phrasing.

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