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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to restate that. The description adds useful behavioral detail by saying the result contains claims, one per asset. However, it introduces no information about rate limits, auth, or response shape beyond that, and the address-format mismatch weakens confidence in the stated behavior.

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 front-loaded, only three sentences, and each sentence mostly earns its place: purpose, address source, and return shape. The misleading address examples waste some space, but the structure is otherwise efficient.

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?

There is no output schema, so the description needs to explain the return value, and it does say it returns claims one per asset. However, the contradictory address guidance leaves the single required parameter ambiguous, which is a critical completeness gap for a one-parameter lookup tool.

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 coverage is 100%, so the schema already defines the single address parameter. But the description conflicts with the schema: it says the address is an L1 address such as 0x..., bc1..., or ltc1..., while the schema says it is a THORChain address (thor1...). That inconsistency is likely to cause an agent to pass the wrong kind of address, so this is more than a minor omission.

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 gives a specific verb and resource: it returns TCY claimer information for a specific address and says the result is claims, one per asset. It also names list_tcy_claimers as the source, which helps distinguish it from the list operation. It does not explicitly distinguish itself from get_tcy_staker, but the core purpose is clear.

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?

It states a clear use case: checking an individual's TCY claims, and it points to list_tcy_claimers as where the address comes from. There are no explicit when-not conditions, but the intended usage context is understandable.

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