list_analytics

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

Discloses that metrics are periodic snapshots, not real-time, and mentions pagination via cursor. No annotations provided, so the description carries the burden well. Could mention if any latency or auth requirements, but overall transparent.

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?

Three sentences total, each adding value: first sentence gives core purpose, second gives usage guidelines, third notes pagination. No wasted words, front-loaded with key 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?

Given no output schema, the description provides a list of metric names but not the exact return structure. It mentions pagination cursor, which is sufficient. Could be slightly more detailed on response format, but for a list tool it is mostly complete.

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 100%, so baseline is 3. Description adds no additional parameter semantics beyond what the schema provides; it mentions pagination but that is already implied by cursor parameter. No added value.

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 clearly states it lists published posts with per-platform metrics (views, likes, comments, shares, engagement) and distinguishes itself from list_post_results by specifying when to use each. It is specific, has a verb and resource, and differentiates from 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?

Explicitly says use for content performance or top posts, and directs to use list_post_results for delivery success. Provides clear when-to-use and when-not-to-use guidance.

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