threads_get_user_posts

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

No annotations are provided, so the description must shoulder the transparency burden. It adds the context of 'authenticated user' but does not disclose pagination behavior, rate limits, or return format. The inclusion of 'ctx' as an arg not in the schema could confuse an agent.

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 mostly concise but includes the 'ctx: FastMCP request context' line, which is not part of the user-facing schema and adds noise. The purpose sentence is front-loaded, but the Args block is not.

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?

The tool is simple with one parameter and an output schema, so the description needn't detail return values. However, it lacks information about auth requirements beyond 'authenticated user' and doesn't mention pagination or filtering caveats. The ctx discrepancy also detracts.

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?

The schema provides zero description coverage for the limit parameter. The description compensates by explaining 'Maximum number of posts to return (default 10)', giving meaningful semantics beyond the raw schema.

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 states 'Get the authenticated user's recent posts' – a specific verb and resource. This distinguishes it from siblings like threads_get_post (single post) and threads_get_profile.

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?

The description provides no guidance on when to use this tool versus alternatives like threads_get_replies or threads_get_conversation. No exclusions or selection criteria are mentioned.

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