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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered externally. The description adds no behavioral context beyond that — no time window, no pagination, no auth requirements — and 'receipt winners' and 'desired policy/upgrade state' are unexplained.

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 efficient sentence with the resource front-loaded and no filler. The brevity only becomes a liability through underspecification, not verbosity.

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?

One required param, no output schema, no annotations burden — yet the description never clarifies the return shape, the time range of 'history', or the meaning of its jargon. It leaves more questions than it answers for a tool an agent must call blind.

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 0% for the single handle parameter, so the description must compensate. It does identify the input as a 'GitHub handle', which reliably conveys the parameter's meaning, but it gives no format or validity details beyond that.

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 verb+resource ('Return ... for a GitHub handle') is present, but the deliverable is described in opaque jargon ('policy-labelled daily receipt winners'). Nothing distinguishes this from the sibling get_impact_profile, so an agent cannot tell which to pick without opening both.

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, when-not-to-use, or alternative routing guidance at all. With get_impact_profile and compare_profiles as obvious siblings, the absence of any selection criteria 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.