Get one post's stats

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds the useful fact that this is the 'full' metric set and lists the fields, which partly compensates for the absent output schema, but it says nothing about auth, rate limits, or what happens for unpublished posts.

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 dense sentence with the scope constraint ('one published post') front-loaded and no filler. Every listed metric earns its place by previewing the return payload.

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, enumerating the metric categories is genuinely helpful, and both parameters are fully documented elsewhere. Minor gaps remain on draft-vs-published behavior and whether a time window applies.

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 100% — post_id and publication are fully documented in the schema, including the loose hostname matching and default. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 (one published post's stats) and enumerates the metric families returned. The 'one published post' scoping implicitly separates it from aggregate tools like get_analytics, but no sibling is named explicitly.

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?

Usage is only implied by the phrase 'for one published post' — the agent must infer that publication-wide numbers belong to get_analytics/get_email_stats and post content belongs to get_post. No when-to-use, when-not, or alternative is stated.

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