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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the no-side-effect guarantee is largely covered by structured data. The description adds 'Privately' (this is scoped to your own data / requires your key), which is genuine context, but it does not disclose return shape, failure modes, or whether a missing claim is an error or an empty result.

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?

Two short sentences: the verb and resource come first, and the disambiguating 'No new claim or payment' follows immediately. No filler language.

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 one-parameter, read-only, idempotent tool with full schema coverage and rich annotations, the description supplies the essentials: what is read, that it is private, and that no mutation occurs. No output schema exists, so return-value detail is not required; only failure/empty-state behavior is unaddressed.

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?

There is a single agent_key parameter and schema description coverage is 100%, so the schema already documents format, storage advice and the Authorization: Bearer alternative. The description adds nothing parameter-specific, making the baseline 3 appropriate.

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?

States a specific verb (read) and resource (your Dot welcome claim and confirmed transfer receipt), and the word 'my' plus 'No new claim or payment' separates it from the action-oriented siblings speedbot_dot_bonus and speedbot_claim_dot_bonus. It stops short of naming those siblings, so an agent must infer the distinction rather than being told it.

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 clause 'No new claim or payment' implies the tool is a status/read path and not the tool to call when actually claiming, which is useful exclusion guidance. However, no alternative is named explicitly (e.g. 'use speedbot_claim_dot_bonus to claim'), so the routing is left to inference.

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