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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses the payload categories (Scope 1/2/3 emissions, diversity, safety, framework compliance) and that the output is machine-readable XBRL. It omits coverage limits (only NZ CS-tagged NZX reporters, not all NZX companies).

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 core purpose and format before the trigger list. The second sentence is a useful but slightly listy restatement of use cases; nothing is wasted, though it is not maximally tight.

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 an output schema present, return-value detail need not be repeated, and annotations fully cover the safety profile; the description still adds the payload overview. Missing pieces are scope caveats (which companies actually file NZ CS XBRL, coverage years) and routing against the many adjacent ESG tools.

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% and both parameters (ticker, year with latest-available default) are documented in the schema. The description only implies the ticker via 'for an NZX company' and adds no year semantics, so it neither compensates nor regresses — the baseline 3 applies.

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?

States a specific verb (Get) and a precisely scoped resource: machine-readable NZ CS-tagged ESG/climate disclosure for an NZX company. The framework name (NZ Climate Standards) and format (XBRL) inherently separate it from generic siblings like get_esg_data or get_esg_disclosure_benchmark, but no sibling is named explicitly.

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 trigger list ('ESG data, climate disclosures, emissions, diversity stats, or sustainability data in structured format') gives reasonable when-to-use guidance. However, it names no alternatives and gives no exclusions, which is a real gap given heavy sibling overlap with get_esg_data, get_esg_disclosure_benchmark, and get_greenwashing_detection.

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