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

With no annotations provided, the description carries the full burden of behavioral disclosure. It offers only generic qualifiers ('comprehensive') and a vague value proposition ('make informed investment decisions'), without revealing specifics about what data is returned, whether ratings are current or historical, or any limitations. This is insufficient for a tool with zero annotation coverage.

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 short (two sentences), but the second sentence ('Make informed investment decisions based on...') is generic promotional fluff that does not add functional value. The first sentence is informative, but the overall structure includes unnecessary filler, reducing conciseness.

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 tool with one parameter and no output schema, the description is minimally adequate. It names the tool's purpose but fails to elaborate on the nature of the returned ESG ratings (e.g., scores, categories, historical vs. current). Given the lack of annotations and output schema, more detail would improve completeness.

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 input schema has 100% coverage for the single 'symbol' parameter, with a simple description 'Stock symbol'. The description adds no additional meaning beyond the schema, which is adequate given the self-explanatory parameter, matching the baseline of 3.

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 states the tool accesses comprehensive ESG ratings for companies and funds, using a specific verb ('Access') and resource ('ESG ratings'). It distinguishes from sibling tools like getESGBenchmarks and getESGDisclosures by its focus on ratings rather than benchmarks or disclosures, though it does not explicitly name alternatives.

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 description implies usage for obtaining ESG ratings to make informed investment decisions, but it does not provide explicit guidance on when to use this tool versus siblings like getESGBenchmarks or getHistoricalRatings. No exclusions or alternative recommendations are given, leaving the context somewhat vague.

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