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 fully covered. The description adds analytical context (per-framework scoring, requirement-level gaps, mandatory reporter status), but since an output schema already exists, this mostly restates return shape rather than disclosing new behavioral traits such as cost, latency, or NZX-listing prerequisites.

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?

Front-loaded with purpose first, then framework scope, then a return-value enumeration, then usage triggers. Every sentence is relevant, though the return-value list is long and partially redundant against the output schema, which costs a little density.

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 a rich output schema, full annotation coverage, and 100% parameter description coverage, the description only needs to carry purpose and routing — both are present. The one gap is that it does not explain how it relates to the ESG disclosure benchmark and climate gap siblings, which matters in a toolset this dense.

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% with only two parameters, so the schema fully documents 'ticker' and the 'framework' enum. The description implies framework filtering through 'multi-framework comparison' but adds no syntax, default, or interpretation detail beyond what the schema already supplies.

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 gives a specific verb and resource ('multi-framework ESG disclosure gap analysis'), scopes it to an NZX company, and enumerates the three standards scored (TCFD, ISSB/IFRS S2, NZ XRB NZ CS 1-4). It is unambiguous about what the tool computes, but it never differentiates itself from close siblings such as get_esg_disclosure_benchmark or get_climate_gap_analysis, leaving the agent to infer boundaries.

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 final sentence gives explicit triggering conditions: 'Use when the user asks about ESG gaps, disclosure readiness, TCFD compliance, ISSB alignment, or multi-framework comparison.' That is a clear usage context, but there is no when-not guidance and the adjacent benchmark/climate-gap siblings are never named as alternatives.

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