environment

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

With readOnlyHint=true, openWorldHint=true, and idempotentHint=true already declared, the safety profile is fully covered by annotations — the burden on the description is low. The description adds genuine value on top by disclosing the dual-query-style behavior (tickers vs countries) and characterizing rolling/trailing as 'smoothing/summation.' No contradiction with the read-only annotations; the description consistently implies pure data access.

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?

Three dense sentences, each with a distinct job: state the domain, give usage patterns, differentiate from siblings. The 'Available indicators' enumeration replaces longer prose and mirrors the enum. For a 13-parameter dispatcher tool this is appropriately sized — nothing extraneous, nothing missing.

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 complex dispatcher with 13 parameters, an output schema, and safe read-only annotations, the description covers the essential decision surface: domain, parameter-selection strategy, special smoothing behavior, and indicator list. The presence of an output schema relieves it of explaining return values. It could have more explicitly stated the dispatcher pattern (one call = one of three named endpoints) and acknowledged the annual/quarterly dimension, but nothing critical is missing.

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 coverage is 100% with rich per-parameter descriptions, so baseline is 3. The description elevates this by disambiguating the easily-confused rolling (smoothing) and trailing (summation) parameters, and by teaching which parameter family fits which indicator. A minor blemish: the schema's indicator enum example ('get_asset_turnover_ratio') is stale and inconsistent with the actual enum values, which the description partially papers over by listing the three real indicator names.

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?

Opens with a clear domain statement ('Environmental and ESG data') followed by specific, actionable examples mapping indicators to parameters ('For ESG scores... use tickers="AAPL"'). Closes with explicit sibling differentiation ('This is the only tool that accepts BOTH tickers= and countries=') which positions it squarely against the breadth/momentum/volatility family. The verb+resource is specific and the tool's dispatcher role is evident.

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?

Provides concrete when-to-use-which-parameter guidance (tickers for ESG scores, countries for carbon/renewable data) and flags the rolling/trailing behavior with examples. The 'only tool that accepts BOTH' phrasing helps rule out alternatives, though it never names a specific sibling to prefer instead. Loses a point for not addressing when NOT to use this tool (e.g., single-instrument financial metrics that belong to siblings like momentum or valuation).

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