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

Annotations already declare readOnlyHint=true and idempotentHint=true, and there is no contradiction with the description. The description adds output details (prioritized roadmap, risk scores, corrective actions) but no additional behavioral traits such as rate limits, data freshness, or external API dependencies. Thus it meets but does not exceed the lower bar set by 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 informative but wordy, including a role-playing opener ('As a COO') and a redundant keyword list. The main purpose is front-loaded, but the extra sentences and keywords could be trimmed for tighter structure.

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?

With 5 parameters, an output schema, and rich annotations, the description provides sufficient context: purpose, inputs, outputs, and use cases. It does not explain return values (covered by output schema) or async behavior (covered by schema), but overall it is complete enough for an agent to select and invoke the tool appropriately.

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 covers all 5 parameters with descriptions (100% coverage). The description mentions facility identifiers and geographic regions but largely restates schema info without adding new semantic details. It does not explain parameter interdependencies or format specifics beyond what is already in the schema.

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 function: 'identify ESG compliance gaps across manufacturing facilities' using specific data sources (EPA TRI, GRI standards). It also differentiates from siblings by focusing on manufacturing facilities and a remediation roadmap, unlike generic ESG audit tools such as esg_audit_multi.

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 provides clear usage context: 'Ideal for sustainability reporting, regulatory risk assessment, and operational improvement planning' and mentions inputs (facility identifiers or geographic regions). However, it does not explicitly exclude alternatives or name sibling tools, so it lacks explicit when-not-to-use guidance.

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