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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description's only added behavioral context is the 7/30-day window constraint; it says nothing about granularity, per-platform breakdown, or aggregation of the returned KPIs.

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 tight sentence that front-loads the resource and the returned metrics with no wasted words. Nothing could be trimmed without losing information.

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 one-parameter, read-only analytics tool with no output schema, the description says enough to call it correctly and sets expectations for what comes back. It leaves minor gaps such as whether KPIs are broken down by platform or time bucket.

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 0%, so the description carries the burden, and it does restate the allowable window ('7 or 30 days'). However, the schema already encodes these exact values via const 7/30 and default 7, so the description adds confirmation rather than new meaning.

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 (Get) and resource (Autopilot analytics), and enumerates the concrete KPIs returned (views, posts, top performers). No sibling in the list is an analytics tool, so confusion risk is low, but the description never explicitly distinguishes itself from the list_autopilot_* siblings.

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?

The time window ('last 7 or 30 days') frames the scope, so the intended usage is implied, but there is no explicit when-to-use guidance, prerequisites, or routing to an alternative sibling.

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