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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is clear. The description adds context about using specific data sources (EPA TRI, FAOSTAT) and the async option to avoid timeout, which is valuable but not extensive. No contradictions with annotations.

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 very concise—four sentences that are front-loaded. The first sentence states the core purpose and data sources, the second covers inputs, the third outputs, and the fourth gives a usage tip. No unnecessary words, and each sentence 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?

Given the output schema exists, the description doesn't need to detail return values. It covers inputs, outputs, data sources, and an async usage tip. It lacks mention of potential error cases, rate limits, or specific output format details, but for a heatmap generator with good annotations, it is mostly complete.

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 coverage is 100%, so parameters are already documented. The description adds clarifying context: it notes that site_ids and region are alternative inputs ('Input manufacturing site identifiers or geographic regions'), and mentions using async:true to avoid timeout. This adds some meaning beyond the schema, but not enough to merit a higher score than the baseline of 3.

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 generates manufacturing waste heatmaps using EPA TRI and FAOSTAT data for COOs, with specific inputs (site identifiers or geographic regions) and outputs (waste intensity maps, circular economy opportunity rankings, and cost-saving potential). It also mentions the async option to handle timeouts. This purpose is distinct from the many sibling tools, which are unrelated.

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 mentions it is 'Ideal for sustainability strategy and operational efficiency improvements,' providing some context. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or conditions where another tool might be more appropriate. Given the large set of siblings, more guidance would be helpful.

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