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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds essentially nothing beyond that: no auth requirements, no indication of what 'this period' means (billing cycle? month?), and no return or pagination behavior. With annotations carrying the burden, the description's lack of any added behavioral context caps this low.

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 short noun phrase with no filler or redundancy. It is front-loaded and wastes no words, though it is a sentence fragment rather than a properly structured statement of purpose.

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?

For a zero-parameter read tool with no output schema, the description partially compensates by listing the returned items (plan, subscription status, emails, AI drafts used). However, it never states the verb, never clarifies the time window, and gives no sense of the response shape, leaving it only minimally adequate.

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 syntax for the description to clarify, and it introduces none.

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 is a verbatim restatement of the tool title, with no verb stating that it retrieves data. It does enumerate the resources involved (plan, subscription status, emails, AI drafts used), which hints at content, but an agent gets this same information from the title alone, making it a tautology rather than a distinct statement of purpose.

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 guidance on when to call this tool versus siblings such as get_overview or get_campaign_stats, nor any prerequisites or exclusions. The only contextual hint is the phrase 'this period,' which is not enough to route an agent between alternatives.

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