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

The annotations already declare the read-only and non-destructive nature, so the description does not need to restate that. It adds some value by indicating the return composition: latest snapshot plus historical points, but it does not disclose pagination, date-range behavior, or any further constraints.

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?

The description is one concise sentence that front-loads the action and resource, then adds the distinguishing analytics detail. There is no redundancy or unnecessary verbiage.

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 tool with five parameters, no output schema, and zero schema-level descriptions, this definition is too thin. An agent can infer the required platform and accountId, but it cannot fully understand the date-range mechanics, the limit parameter, or exactly how this result differs from list_posts. The read-only annotations reduce safety concerns but do not fill the comprehension gap.

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 must compensate for the five parameters. It only loosely maps accountId to 'connected account' and platform/status to 'published posts'. The lifecycle of limit, startDate, and endDate is left entirely 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 states a clear action ('List'), resource ('published posts'), and differentiating scope ('with their latest analytics snapshot and historical points') for a connected account. It is distinguishable from the sibling list_posts by the addition of analytics, though it does not explicitly name that alternative.

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 guidance is given about when to use this tool instead of list_posts or get_post_analytics. The phrase 'for a connected account' implies a precondition, but no alternatives, exclusions, or decision criteria are provided.

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