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

Annotations declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, yet the description never mentions that this is a mutating operation, what it writes or destroys, or what permissions/consent it needs. It also omits that supplier data and prior-agent context are transmitted to an external inference provider (the consentExternalProcessing parameter is the only clue), and says nothing about the payment/invoice path.

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?

It is a single front-loaded sentence with no filler, which is structurally sound, but the brevity is under-specification rather than economy given the tool's complexity. Nothing about the input contract or the write behavior is front-loaded because nothing is said at all.

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?

A destructive, open-world, six-parameter tool with a required nested input object, a mandatory consent flag and no output schema needs far more description than one clause. Critical facts an agent must know before calling — that it mutates state, that external processing requires consent, that an idempotency key is required — are absent from the description.

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?

With 67% schema coverage the baseline would be 3, but the description adds zero meaning beyond the schema for any of the six parameters. It does not mention the mandatory framework choice (CSRD/GRI/SASB), the vendor-master CSV shape, the 75,000-character combined limit, idempotencyKey semantics, or sourceRunIds/sourceFields chaining to prior runs.

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 verb-plus-resource ("Assess ... supplier ESG evidence, disclosures and certifications") is identifiable and the trailing clause hints at gap reporting, so an agent can tell this is an ESG assessment tool rather than risk scoring or bid scoring. But the actual deliverable — a score? a rating? a gap report? — is never stated, and the name/title promise "scoring" that the description only implies.

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?

There is no when-to-use guidance, no prerequisites, and no routing to or away from any of the many siblings (supplier-risk, xclause-risk-scoring, xscore-bid-evaluation, xvendorbench). An agent must infer the selection criteria entirely from the tool name.

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