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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds useful value by enumerating the counters returned, but says nothing about pagination behavior, default ordering, or result size limits.

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 compact sentence with the resource and the payload front-loaded, zero filler. It is a noun phrase rather than a sentence, which slightly weakens the framing of the action but wastes no space.

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 output schema, the description's enumeration of returned counters is genuinely helpful. However, for a 5-parameter filtered, paginated list tool it omits how filters combine and how paging works, leaving real gaps an agent would need to guess at.

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 60%, below the 80% threshold, so the description should compensate for the undocumented parameters. It adds no meaning for page, type, search, or status beyond what the schema already provides (enum values, 'Filter by name'), leaving the filter semantics unexplained.

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 the resource (push mailings) and states the returned metrics (targets, sent, shown, clicked, revenue), which lets an agent distinguish this list endpoint from analytics siblings like get_push_analytics or get_push_overview. The verb 'list' is only implied by the name rather than stated, keeping it short of a 5.

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 statement of when to use this tool versus alternatives such as get_push_overview, get_push_analytics, or list_campaigns, and no guidance on pagination or when to apply the available filters. The agent must infer usage entirely from the name.

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