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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond those annotations by explicitly stating 'This tool does not spend money' and warning about the need for owner authorization before payment-capable actions—useful behavioral context for an agent.

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 with no filler. The primary purpose is front-loaded, and the critical non-spending and authorization caveats are placed immediately after without bloating the text.

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 simple, zero-parameter informational tool, the description is complete: it states what the tool returns (instructions), the subject of those instructions, and the key safety/authorization context. No output schema or additional details are necessary for 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?

The tool has zero parameters and 100% schema coverage, so the baseline is 4. The description adds meaningful scope by explaining what the instructions relate to, which is sufficient given there are no parameters to document.

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 uses a specific verb and resource: 'Get instructions for the optional one-time 10 USDC Speedbot Pro upgrade on Base.' It clearly distinguishes this from sibling info tools by naming the exact upgrade context, and clarifies it is informational rather than an action.

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 frames when this tool is relevant: when a user needs instructions for the Speedbot Pro upgrade. It also provides an important prerequisite by stating that owner's payment authorization must be obtained before using a wallet or payment-capable HTTP client. It does not explicitly name alternative sibling tools, but the use case is clear.

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