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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds complementary context by mentioning data sources (WITS, CDP) and the output breakdown. The async:true guidance to avoid timeout is a valuable behavioral detail not present in annotations. No contradictions found.

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 concise at three sentences, covering purpose, input, use case, and async tip without redundancy. The opening 'As a COO' is minor but not distracting, and the structure is front-loaded with the core function.

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 read-only rater with an output schema and rich annotations, the description covers the essential aspects: data sources, output dimensions, use cases, and performance guidance. It doesn't explicitly state the geographic scope boundary, but that is implied by the tool name and target audience.

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%, so the baseline is 3. The description adds practical meaning for institutionName ('name or identifier') and explains async's purpose ('avoid timeout'), going slightly beyond the schema. Year and countryCode are clear from the schema alone, so the description doesn't need to repeat them.

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 specifies the tool's function: evaluating ESG compliance of African trade finance providers using WITS and CDP data, and returning a breakdown across environmental, social, and governance dimensions. This distinguishes it from sibling ESG tools by focusing on a specific target (African trade finance) and methodology.

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 provides clear usage context: 'Ideal for due diligence on trade partners or portfolio risk assessment.' It does not explicitly name alternative tools or exclusion criteria, but the use case is specific enough for an agent to make an informed choice.

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