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

With no annotations, the description carries the behavioral burden and does disclose key traits: newest-first ordering, included view/like/comment counts, and cursor-based pagination. It omits auth/error/rate-limit details, but for a simple read endpoint the named behaviors are the most decision-relevant ones.

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 first sentence is concise and front-loaded, but the remaining platform-by-platform list becomes a dense block of text. It is informative and mostly necessary, though the phrasing 'for posts' adds ambiguity and the format could be more scannable with line breaks or structured formatting.

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 annotations and no output schema, the description covers the key usage details: result ordering, returned metrics, pagination, and platform-specific id formats. It does not mention authentication or supported platform enum values explicitly, but the platform list is inferable and the core calling contract is present.

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 0%, yet the description compensates thoroughly: it enumerates every supported platform, gives accepted user-identifier and post-identifier forms for each, and defines the cursor as next_cursor from a previous response. This is far more than the bare property names provide.

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 identifies the resource as a user's posts and specifies ordering and returned counts, so an agent can distinguish it from get_user or get_post by resource type. The only slight weakness is that the later 'for posts' ID-format clauses could be read as implying single-post retrieval, adding ambiguity.

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 clear context that this endpoint is used to fetch a user's posts, and it instructs on pagination with next_cursor. It does not explicitly name alternatives or exclusions (e.g., use get_post for a single post), so it stops short of a 5.

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