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

Beyond the annotations (which already declare a safe read), the description discloses ordering and pinning behaviour, the protected-account visibility rule behind a 404, and a detailed credit model including the extra per-page profile lookup on the first page only. That is exactly the kind of cost and failure context an agent cannot get from structured fields.

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?

Purpose and ordering are front-loaded, then error semantics, then billing, then pagination — a sensible order with no filler sentences. The billing information is slightly redundant, since 'Billed per post returned' is restated in the full credit breakdown.

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 still tells the agent what comes back (ordered posts with pinned post first), how to continue paging via meta.nextCursor, what a 404 means, and what each call costs. Nothing needed to invoke or iterate this tool correctly is missing.

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%, so user, limit, and cursor are already fully documented, including cursor reuse rules. The description adds little parameter-level detail beyond noting that the cursor carries the account forward on later pages, which is a marginal extension over the schema baseline.

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 gives a specific verb and resource and then pins down the exact result set: 'Returns the profile's Replies tab: the account's posts together with its replies to others.' That definition lets an agent distinguish it from get_x_user_posts (posts only) and get_x_replies (replies to a single post) without opening any schema.

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?

It gives concrete operational guidance: paginate by re-calling with meta.nextCursor as the cursor, and expect a 404 when the account is missing or protected. It stops short of naming sibling alternatives for posts-only or thread retrieval, so the agent must infer those choices from the result-set definition.

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