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

Annotations only declare readOnlyHint=false, so the description carries the weight of explaining behavior, and it does so substantively: maturation begins at day 20 and uncollected entitlements are cancelled at day 40 and returned to the pool. This lifecycle disclosure is genuinely useful context beyond the annotation. It stops short of covering idempotency, auth requirements, or what a partial collection looks like.

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, no filler, with the action front-loaded and the window constraints following. Every clause earns its place by conveying either the action or a hard deadline rule.

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 parameters and no output schema, the description's job is to convey action and constraints, which it largely does. It could have noted what the agent receives on success (coin amount credited) or whether the call is idempotent, but for a zero-argument batch action the coverage is solid.

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 takes zero parameters, so there is nothing for the description to disambiguate at the argument level. The baseline of 4 applies; the description correctly avoids inventing parameters.

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: 'Collect every matured RACOIN entitlement.' It is clearly a collection/claim action on RACOIN, distinct from coin viewing or sending siblings. It does not, however, explicitly distinguish itself from the similarly named project100_claim sibling, so sibling differentiation is left to inference.

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?

There is no explicit when-to-use vs alternative guidance, but the timing constraints ('Nothing matures before day 20') implicitly tell the agent not to invoke this before entitlements mature. The absence of explicit routing to alternatives such as project100_claim keeps this at implied rather than stated guidance.

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