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

Annotations declare destructiveHint=true and openWorldHint=true, yet the description says nothing about what is mutated or overwritten, that data is sent to an external inference provider, or that results may be provisional. For a destructive, open-world tool the description should carry this context explicitly; it does not. The only hints live in the schema, not the description.

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?

A single front-loaded sentence with no filler. Efficient, though its brevity contributes to the gaps elsewhere rather than reflecting deliberate economy.

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?

This is a high-complexity tool with nested inputs, a 75k character limit, consent gating, idempotency keys, prior-run sourcing and destructive semantics — and no output schema to explain returns. The description covers none of it, leaving an agent without enough to call it safely or 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 coverage is 67%, and the description contributes zero parameter meaning. Two parameters (sourceFields, sourceRunIds) have no schema descriptions at all and are completely unexplained — their role in pulling prior-agent context is invisible unless the agent reads the enum values. Baseline can't be raised because the description adds nothing beyond structured fields.

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?

States a specific verb (Find) and resource (spend data) plus three concrete detection targets: off-contract purchases, unapproved suppliers, split orders. An agent can grasp the deliverable immediately. It does not differentiate itself from siblings like xspend-taxonomy or xscore-bid-evaluation, which keeps it from a 5.

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?

No when-to-use guidance, no prerequisites (e.g. that approvalPolicy defaults stay provisional, or that consentExternalProcessing is mandatory), and no named alternatives among the many sibling spend/compliance tools. The agent must infer placement in a workflow from the name alone.

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