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

Annotations already cover readOnly, openWorld, and idempotent hints, lowering the bar. The description adds context about data sources (CDP open data, UNCTAD STAT) and output structure (severity, location, source verification), which is useful but could include more about freshness or limits.

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 front-loaded with purpose, then inputs/outputs and data sources, all in three sentences. It is compact and informative, though the trailing keyword list is slightly redundant but not harmful.

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?

Given the tool's moderate complexity, the presence of an output schema, and strong annotations, the description sufficiently covers what the tool does, its data sources, and key outputs. It lacks alternative recommendations but remains complete for an agent to select and invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description lists core inputs (region, incident type, time range) but does not add new semantic details beyond what the schema already provides for each parameter (e.g., enum values, date formats).

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 'Tracks real-time ESG incidents in logistics networks for COOs', which is a specific verb+resource with a defined audience. It distinguishes from siblings by scoping to logistics networks and listing example incident types, making its unique purpose 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?

The description implies usage for COOs needing real-time ESG incident data, with input/output examples. However, it does not explicitly specify when to use this tool over alternative ESG-related siblings like supplier_esg_audit or sustainability_report, nor does it provide exclusion criteria.

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