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 structurally. The description adds the returned dimensions (volumes, counts, fees), which is useful context, but says nothing about auth requirements, scoping, or aggregation 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?

A single front-loaded sentence that names the resource and the returned fields with no filler or redundancy.

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 carries the full descriptive burden, and while it names the returned dimensions it leaves the 'by thorname' scoping unexplained, which is the one thing an agent would need clarified to call it correctly.

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 schema declares zero parameters, which normally sets a baseline of 4, but the phrase 'by thorname' implies a selectable/filtering key that no parameter actually supplies. That mismatch creates ambiguity about whether the tool is genuinely parameterless or implicitly scoped, so it falls just below baseline.

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 ('Returns affiliate statistics') and lists the returned content (volumes, counts, fees), which is more than a tautology. However it does not differentiate itself from sibling affiliate tools like get_affiliate_earnings and get_affiliate_history, so an agent cannot tell which affiliate endpoint 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?

There is no when-to-use guidance and no mention of alternatives, despite three closely related affiliate siblings (earnings, history). The agent is left to infer the distinction entirely on its own.

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