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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context — a real-time snapshot ('right now'), per-stock granularity, and the fact that the mutation happens outside this tool — but says nothing about auth requirements, pagination, or whether results can be empty.

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, front-loaded with the payload ('creator fees a wallet can claim right now'). The second sentence is tangential to retrieval but earns its place by clarifying that claiming is out of scope for this tool.

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 single-parameter read-only lookup with no output schema, the description supplies enough to call it correctly and understand the return granularity ('per stock'). Minor gaps remain around the wallet format and empty-result behavior, but nothing critical is missing.

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 one parameter with 0% schema description coverage; the description implies the wallet is the subject of the query but gives no format, chain, or address-type guidance to compensate for the schema gap. Marginal value over the schema field name alone.

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 names a specific resource (creator fees a wallet can claim) and a scope modifier ('right now, per stock'), which cleanly separates it from siblings like fee_schedule (fee rates) and get_coin (asset data). It is clear what is returned without opening the schema, though it never explicitly names an alternative sibling.

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 sentence 'Claiming is one transaction on the portfolio page' implicitly routes the agent: this tool only reads claimable amounts, while the actual claim happens elsewhere. However, it never states when to prefer this over a sibling or any exclusions, so usage is only implied rather than spelled out.

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