getESGDisclosures

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds nothing behavioral — no indication of what a 'disclosure' contains, whether results are historical or current, or how it differs from an ESG rating. With annotations carrying the basic profile, a 3 is the fair ceiling.

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?

It is short — two sentences — but the space is spent on brand language rather than front-loading the operation, the input, or the output. Brevity here reflects missing substance rather than disciplined editing.

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 simple one-parameter read tool with full schema coverage and annotations, the description still needs to say it returns ESG disclosure data for the given symbol and how that differs from ESG ratings. Instead it describes a different kind of tool entirely, leaving the agent's core question unanswered.

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?

The schema documents the single 'symbol' parameter at 100% coverage, which would normally anchor a 3, but the description actively undercuts it by describing criteria-based discovery ('scores, performance, controversies, business involvement criteria') when no such filter parameters exist. That creates a false expectation about the input rather than adding meaning.

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 uses promotional framing ('Align your investments with your values', 'Discover companies and funds based on... criteria') that reads like a screening/search tool, while the tool actually takes a single required 'symbol' and returns ESG disclosures for it. It never states the concrete verb+resource (fetch ESG disclosure records for one symbol), so an agent cannot confidently distinguish it from marketing copy.

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?

There is no explicit when-to-use guidance and no mention of the many closely related siblings (getESGRatings, getESGBenchmarks, getDisclosure, getFundDisclosure, searchFundDisclosures). The phrase 'Discover companies and funds' implies a search workflow that this single-symbol tool does not support, so the only usage signal present is misleading rather than helpful.

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