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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds the content scope ('including fees collected by thorname'), which is useful, but says nothing about auth needs, aggregation window, or why the call is non-idempotent despite being a read.

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?

A single front-loaded sentence with no filler. It is appropriately sized, though its brevity comes at the cost of the routing information a zero-param tool with many siblings would benefit from.

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?

No output schema exists, so explaining return values is not required, and the zero-param schema is trivial. Still, for a tool sitting among several near-identical affiliate endpoints, the description does not supply enough to confidently select it over its siblings.

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 the baseline is 4; there is no parameter semantics for the description to elaborate. The description does not misrepresent the (empty) input contract, though it also adds nothing about implicit scoping.

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 ('Returns') and resource ('affiliate earnings') plus a scope detail ('fees collected by thorname'), so the agent knows what the tool retrieves. However, it does not distinguish itself from the three sibling affiliate tools (get_affiliate_history, get_affiliate_stats, get_earnings_history), leaving ambiguity about which one to pick.

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 description provides no when-to-use guidance, no prerequisites, and no explicit alternatives. With get_affiliate_history, get_affiliate_stats, and get_earnings_history as close siblings, the absence of any routing cue is a real gap.

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