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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description goes beyond them by disclosing the data model: a monthly rollup of earning_events + amount_base_units, recent rows carrying crank_amount that is null while unpriced, and a $CRANK-only limitation with no USD figure. That is genuinely useful behavioral context an agent cannot derive from the schema.

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?

Both sentences are compact and front-loaded, with no filler. But the density works against it: undefined internal terms like earning_events, amount_base_units, and crank_amount are dropped without explanation, making the text cryptic rather than merely concise.

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?

An output schema exists, so return values need not be enumerated, and annotations carry the safety contract. What remains missing is any indication of how integrator_wallet_address is scoped or what limit/caller_id do, and no guidance on when to prefer this over related stats endpoints. Adequate but with clear gaps.

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 description coverage is 0% across all three parameters (integrator_wallet_address, limit, caller_id), so the description carries the full burden. It says nothing about any parameter, not even the required wallet address or the default limit of 100, leaving the agent to infer meaning purely from names.

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 and scope: integrator $CRANK reward rows, split into per-action and per-month aggregations. That is more than a name restatement. However, it never names the closely-related sibling (get_integrator_stats) or explains how the two differ, so sibling differentiation relies on 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 when-to-use statement and no alternative named. The only usage-relevant word is 'Read-only,' which merely restates annotation coverage rather than telling the agent when this tool is the right choice over get_integrator_stats or get_usage_report.

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