getESGBenchmarks

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. Beyond that the description adds almost no behavior: it doesn't say what is compared, whether the year scopes the benchmark set, whether industry grouping is automatic, or what happens when year is omitted.

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?

Two sentences, front-loaded with the resource name, which is good. The second sentence's closing clause about responsible investment decisions is promotional filler that doesn't help an agent decide anything.

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?

There is no output schema, so the description carries the burden of explaining the return shape, and it doesn't — an agent cannot tell whether this returns industry-level benchmark percentiles, per-company ESG scores, or fund comparisons. For a tool with no output schema and no siblings differentiated, that is a substantive gap.

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?

With a single optional parameter at 100% schema coverage, the schema already explains 'year', so the baseline of 3 applies. The description adds nothing further, such as a year format or the consequence of leaving it out.

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 names the resource (ESG benchmarks) and a comparison action, plus the API name, so the domain is clear. But it never states what the tool actually returns or how it relates to close siblings like getESGRatings and getESGDisclosures, leaving the agent unsure which ESG endpoint to pick.

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 when-to-use guidance and no mention of the two obvious alternatives (getESGRatings, getESGDisclosures) that share the ESG namespace. The phrase about making 'informed and responsible investment decisions' is aspirational marketing rather than a usage condition an agent can act on.

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