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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds useful behavioral context: this tool returns a payment link, and the actual payment flow continues by POSTing to paymentLink to receive an HTTP 402 challenge. It does not cover auth needs or rate limits, but it goes beyond what the annotations state.

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?

Two short sentences, front-loaded with the return value and followed by the required follow-up action. No wasted words.

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 tool has four required, nested object parameters with no schema descriptions, and the description does not compensate by explaining their structure or meaning. Output schema and annotations exist, but an agent still lacks enough context to construct a correct invocation.

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 0% and the description provides no explanation of any of the four required parameters (consumer_id, assurance_record, evidence_artifacts, invocation_context). Saying 'POST the same arguments' does not define those arguments.

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 states a specific verb and resource: returning a Stripe MPP payment link for a Blue Cap capability. It distinguishes the MPP variant implicitly from the non-payment sibling evidence_verify, though it does not name that sibling or explain the relationship directly.

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 gives a next-step procedure (POST the same arguments to paymentLink to receive an HTTP 402 challenge) but does not say when to choose this tool over evidence_verify or any other sibling. No exclusions or usage context are provided.

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