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

readOnlyHint=true already declares this a safe read, so the description only needs to add context. It does so usefully by disclosing the shape and meaning of the returned data (per-validator attribution, redeemable XRD, maturity flag), which tells an agent why it would call this before a claim. Pagination or result-size behavior is not addressed.

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 sentences, no filler. The core scope (what is listed) is front-loaded, and the second sentence is purely actionable routing information. Every clause 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?

With no output schema, the description must convey the return shape, and it does name the salient fields an agent needs to decide whether to proceed to a claim. It leaves minor gaps: whether all NFTs are returned or the list is bounded/paginated, and what an empty result implies.

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?

Both parameters are fully documented in the schema, including the mainnet/stokenet enum and the account_… address format, so the schema carries the burden. The description adds no parameter-level detail (e.g., network defaults or address validation), which matches the baseline 3 when coverage is 100%.

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 and resource: it lists the stake claim NFTs an account holds, and goes further by naming the three attributes returned (minting validator, redeemable XRD, maturity). This is well beyond a tautology and is clearly distinct from generic siblings like get_nft_data or list_validator_operations, though it never explicitly contrasts itself with any of them.

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?

Gives clear downstream context by naming the sibling and the intent: feed the matured NFTs to build_validator_manifest as a claim-xrd operation. That effectively describes the workflow this tool feeds. It stops short of stating exclusions, such as when to prefer get_nft_data or what to do with unmatured entries.

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