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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond annotations: it explicitly states 'Free read' and provides SAP MCP execution guidance covering pricing (free, no x402), routing (direct hosted call), and signer boundary (keypair bytes never received). This enriches the behavioral profile without contradicting the annotations.

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 split into two paragraphs: the first is a concise, informative purpose statement with filters and paging; the second is a standardized SAP MCP execution guidance block. The content is efficiently packed without unnecessary fluff, and the main purpose is front-loaded. The second paragraph is somewhat boilerplate but adds operational context, so it earns its place.

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 read-only tool with 4 parameters (1 required) and an output schema, the description covers the purpose, parameter semantics, and execution guidance. It does not explicitly describe the return format, but the presence of an output schema mitigates that need. The description is sufficient for an agent to know when and how to call it, though it could benefit from a concrete example of the return value or an explicit mention of the response shape.

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 has 100% description coverage for all 4 parameters, so the baseline is 3. The description adds meaning beyond the schema by listing the exact allowed kinds for the 'kind' filter ('buyback, external_buyback, burn, claim, creator_payout') and specifying the default ('buyback+external_buyback+burn'). This is valuable semantic detail that the schema's generic 'comma-separated event kinds filter' lacks.

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 action ('Fetch'), a clear resource ('buyback / burn / fee transaction events'), and a precise scope ('for one PerpsPad token'). It also explains the underlying mechanic ('backing perp PnL drives buybacks and burns'), making the purpose unambiguous. The singular 'one token' distinguishes it from sibling plural getters like sap_perpspad_get_tokens.

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 clearly implies when to use this tool (to fetch events for a single token) but does not explicitly contrast it with sibling PerpsPad tools (e.g., get_token, get_tokens). It does not state exclusions or say 'use this instead of X when...'. Usage is inferred rather than explicitly directed.

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