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

Annotations declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=true, but the description says only 'Assess' and does not disclose destructive side effects, external processing, payment requirements, or idempotency behavior. 'Assess' may suggest a safe analytical operation, so the description adds little behavioral context beyond the domain list.

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 a single front-loaded sentence with zero boilerplate, leading with the verb and immediately enumerating the assessment areas. Nothing in the sentence is extraneous.

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?

For a complex six-parameter service with a nested inputs object and no output schema, the one-sentence description is insufficient. It does not explain how to invoke the service, what outputs to expect, how consent or payment fields work, or what happens to source documents and prior-agent context.

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 67%, with several parameters documented only in the schema, and the description does not explain any invocation parameters such as inputs.context, categoryEvidence, sourceFields, sourceRunIds, consentExternalProcessing, or paymentInvoiceId. It adds thematic context but no parameter-level meaning beyond what the schema provides.

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 uses a specific verb, 'Assess,' and names the software/SaaS and cloud buying domain with concrete assessment areas such as licenses, renewals, security, data residency, and exit terms. It distinguishes this category agent from siblings like it-hardware and telecom by domain, though it does not explicitly name the alternatives.

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 software and cloud buying assessments, but it gives no explicit when-to-use guidance, no exclusions, and no routing to sibling tools such as it-hardware or negotiation. The category scope is inferable but not operationalized.

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