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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds useful behavioral context about output bands (0-100, Exemplary/Strong/Adequate/Limited/Minimal) and per-dimension breakdowns, but says nothing about failure modes, whether the ticker must be NZX-listed, or data freshness. Adequate, not rich.

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?

Four sentences, well front-loaded: identity first, then the dimension breakdown, then the return shape, then the when-to-use triggers. Each sentence carries information, though the return-value sentence partially duplicates the output schema and could be trimmed without loss.

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 single-parameter, read-only scoring tool with an output schema available, the description covers purpose, scoring dimensions, rating bands, and invocation triggers, which is nearly everything an agent needs. The remaining gap is minor: no statement about coverage universe restrictions or behavior for an unrecognized/foreign ticker.

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?

There is a single required parameter and schema description coverage is 100%, with the schema itself supplying format and example ('NZX ticker symbol (e.g. FPH)'). The description only implies the ticker via 'for an NZX company' and adds no format, casing, or exchange-scoping detail beyond the schema, so 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 and resource ('Get the NZX Disclosure Transparency Score for an NZX company') and immediately enumerates the five scoring dimensions, so the agent knows exactly what metric is produced. It is clearly distinguishable from nearby siblings such as get_disclosure_language, get_esg_disclosure_benchmark, and get_annual_report_quality without opening any schema.

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 trigger phrases ('disclosure quality, transparency score, reporting transparency, or how well a company communicates with the market'), which is strong positive routing guidance. It does not, however, say when to prefer this over adjacent siblings like get_ir_quality or get_disclosure_language, so it stops short of full alternative-based guidance.

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