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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description reinforces this with 'Read-only SAP SDK wrapper' and adds critical context about signer boundaries ('hosted reads/builders never receive keypair bytes'). No contradictions.

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 front-loaded with the core action but includes lengthy, repetitive guidance that could be streamlined. While informative, the repeated execution guidance in both description and input schema reduces conciseness.

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?

Given the single parameter, high schema coverage, annotations, and presence of output schema, the description provides sufficient context. It covers usage intent, constraints, and workflow integration, making it complete for the tool's complexity.

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?

The sole parameter 'disputePda' is fully described in the schema (base58 type). The description adds context by naming it a 'V2 dispute PDA', which enhances semantic understanding without redundancy. Schema coverage is 100%, but the description still adds value.

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 explicitly states 'Fetch a V2 dispute PDA', using a specific verb and resource. It clearly distinguishes itself as a read-only operation within the SAP ecosystem, with no ambiguity.

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 provides extensive guidance: it states the intent (read/discovery), when to use (before mutating), and explicit alternatives (sap_estimate_tool_cost, sap_payments_call_paid_tool). It also specifies pricing and routing steps, giving clear context for agent decision-making.

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