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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, so the tool's safety profile is clear. The description adds behavioral context by noting it 'analyzes covenant text against regulatory benchmarks' and 'receive structured compliance insights with source references,' which goes beyond the annotations to describe inputs and outputs.

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 three sentences with efficient front-loading: purpose first ('quickly assess'), then details on what it analyzes and delivers, then use cases. No redundant phrases or filler, making it appropriately sized and well-structured.

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?

The description covers purpose, use cases, and output type ('structured compliance insights with source references'), and an output schema exists to document return values. It does not explicitly address limitations, prerequisites, or differentiation from all overlapping siblings, but overall it is complete enough for a read-only analysis tool.

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 parameter meanings are fully documented in the schema. The description itself adds little parameter-specific information beyond generic 'Input bond covenant details,' but the baseline of 3 applies because the schema does the heavy lifting.

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's function: 'assess whether your bond covenants meet ESG compliance standards set by BIS and ECB.' It specifies the resource (bond covenants), the action (assess compliance), and distinct focus areas (carbon emissions, governance, social impact), distinguishing it from sibling tools like bond_covenant_monitor or syndicated_loan_covenant_breach_alert.

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 explicitly names use cases: 'pre-issuance due diligence or ongoing monitoring of existing bond portfolios.' It does not mention alternatives or exclusions, but the 'Ideal for' phrasing implies typical contexts without explicitly naming when not to use the tool.

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