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

The description frames this purely as a read ('Fetch analytics', 'Returns account-level summary data'), yet annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. A fetch-and-return tool being flagged destructive is a direct contradiction the agent has no way to reconcile. Flagged as an annotation contradiction.

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?

Two compact sentences, front-loaded with the core action and followed by the return behavior. No filler, though the second sentence is somewhat dense about fallback behavior.

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?

An output schema exists, so return values need not be explained, and the description does convey what data comes back. But the behavioral picture is incomplete and actively conflicted against the annotations, leaving the agent unsure whether this call mutates state.

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 description coverage is only 50%, so the description should compensate for the undocumented parameter. It adds no parameter detail at all - neither the meaning of recentLimit nor the platform enum values are explained beyond what the schema already carries.

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 ('Fetch analytics for a connected platform') and clarifies the two data sources it returns. However, it does not distinguish itself from the overlapping sibling get_stats_insights, so an agent cannot tell which to pick from the description alone.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The sibling get_stats_insights plausibly overlaps in scope, and nothing routes the agent between them.

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