Fetch Pending Settlement

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds minimal behavioral insight beyond repeating the read-only nature and mentioning the underlying RPC and program, without disclosing rate limits, error behaviors, or permission requirements.

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 two sentences long, efficient, and front-loaded. However, the second sentence mixes context and guidance into a somewhat dense phrase, slightly affecting readability.

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 presence of an output schema and comprehensive annotations, the description adequately covers the tool's role within the SAP ecosystem, referencing read-only chain state inspection for mutations. It assumes familiarity with SAP concepts but is sufficient for informed use.

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 100% with the single parameter clearly described in the schema as 'Pending settlement PDA (base58) to fetch'. The description adds no further meaning to the parameter, consistent with the baseline of 3.

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 clearly states the tool fetches a 'V2 pending settlement PDA', which is a specific resource and action. However, it does not distinguish this fetch from other SAP fetch tools like sap_fetch_attestation, as all 'sap_fetch_*' tools share the same read-only wrapper context.

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 inspecting chain state before mutations ('Use these reads to inspect current chain state before mutating...'), but does not specify when not to use it or suggest alternatives. No prerequisites or exclusions are provided.

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