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

Annotations already indicate readOnly, idempotent, and openWorld hints. The description adds value by explicitly requiring async:true to avoid x402 timeout and by disclosing output types (waste classification, cost impact estimates, recommendations). This complements the annotations without contradiction.

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 and front-loaded with the core purpose, followed by waste types and input/output summary. The appended async note is slightly awkward but necessary and justifiable. No redundant filler.

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?

With an output schema and safety annotations present, the description provides sufficient context: audience, data source, outputs, and the critical async requirement. It does not delve into six_sigma_tool options or include_ted_data behavior, but the schema's enums and defaults mitigate this 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?

Schema coverage is 67%, and the description names procurement category, time period, and organizational unit, but these are already documented in the schema. It does not explain six_sigma_tool or include_ted_data beyond what the schema offers (enum/default), though it adds contextual meaning for DMAIC and EU TED data.

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: analyzing procurement waste for COOs with Six Sigma DMAIC and EU TED tender data. It also specifies the types of waste identified (non-value-added activities, overprocessing, inefficiencies), which distinguishes it from generic analytics tools.

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 appropriate usage context through audience (COOs), framework (Six Sigma), and data source (EU TED), but it does not explicitly state when to use this tool over alternatives or when not to use it. There are no exclusions or alternative tool references.

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