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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered without help from the description. The description adds real context by enumerating the possible status values (waiting, needs_approval, sent, failed) and by disclosing the underlying GET endpoint, but says nothing about ordering, pagination, or what is omitted.

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 short clauses with the [read-only] marker and the status enumeration front-loaded, and no filler. The opening noun phrase reads slightly awkwardly as a description of an action, but nothing is wasted.

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, the description carries the return-shape burden and does partially meet it by naming the status field and the resolved text. It omits pagination, ordering, and the shape of reshare entries, leaving gaps for a list tool returning unknown volume.

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% for the single, ambiguously named `id` parameter. The parenthetical endpoint template (GET /api/v2/posts/{id}/comments) does implicitly resolve `id` as a post identifier, which is the one useful clarification the description makes, but it never states this directly.

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 names a specific resource — a post's comments-after-publish and reshares — and enumerates the status field values, which is enough detail to distinguish it from add_post_comments and get_post. It stops short of explicitly contrasting itself with siblings, but the scope is clear.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent must infer from the name alone that this is the retrieval counterpart to add_post_comments.

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