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

Annotations already mark readOnlyHint and idempotentHint. The description adds valuable behavioral details: reading extends the pad's life by 30 days, costs $0.001 per call via x402, and the paying wallet serves as identity. No contradictions with 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 concise at 4 sentences, front-loading the main purpose and adding specifics about usage (raw parameter), behavioral effects (life extension), and cost. Every sentence adds value without redundancy.

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 (context), the description appropriately focuses on input and behavior. It covers reading scratchpads across sessions, the identity mechanism, the raw option, and cost. No critical gaps for a read operation.

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 covers both parameters at 100%. The description adds context: '?raw=1 returns the bare document instead of the JSON envelope', which clarifies the raw parameter's effect. However, it does not explain that the 'name' parameter is optional (required array empty) or what happens if omitted.

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 verb 'Read' and the resource 'one of your wallet's scratchpads'. It specifies the scope (any session, any machine) and differentiates from sibling tools like 'post_scratchpad_name' (write) and 'get_scratchpad' (possibly without name).

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 usage guidance on the '?raw=1' parameter and notes cost and life extension. However, it does not explicitly state when not to use the tool or mention alternatives to help differentiate from siblings like 'get_scratchpad'.

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