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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safety profile is covered. The description adds useful context about data sources (EPA GHGRP, MSCI ESG methodology) and cost, which helps the agent understand what it is getting, but it doesn't describe output shape or pagination; with annotations handling safety this is adequate.

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 compact and front-loaded with the main purpose, followed by sources, audience, and price. Every sentence adds information, although the pricing and audience could arguably be omitted without losing selection-critical meaning.

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?

For a read-only benchmark tool with zero required parameters and clear enums, the description covers purpose, content, and sources. It does not document the return payload and there is no output schema, but the benchmark nature makes the output reasonably predictable; still, an agent would benefit from knowing result granularity or format.

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 0%, so the description must compensate for the two parameters focus and sector. The description's mention of sector-based benchmarking and the enumerated metric categories (carbon, social, governance components) partially maps to the focus enum values, and 'by sector' maps to sector. This adds meaning beyond the bare enum names, though it does not explicitly name each parameter.

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 specifies the tool returns ESG benchmarks by sector, enumerating the specific metrics (carbon intensity, net zero commitments, SBTi alignment, board independence, pay equity, composite scores) and data sources. It is distinguishable from siblings by the 'ESG' and 'sector' framing, though it doesn't name a sibling it differs from.

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 audience line 'For sustainability agents and ESG analysts' gives some usage context, but there is no explicit when-to-use or when-not-to-use guidance, nor a named alternative among the many sibling benchmark tools. The pricing note is operational but doesn't help select between alternatives.

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