threads_get_posts

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

With no annotations provided, the description carries the burden of disclosing behavior. It states the operation is a read ('Fetch'), scopes to the authenticated user, and describes the return as a JSON string with posts and pagination info. It does not cover rate limits or error cases, but the disclosed behavior is sufficient for basic invocation.

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 concise, front-loaded with the core purpose, and uses a clear Args/Returns structure. Every sentence serves a purpose without redundancy.

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 two optional parameters, and the description covers both, describes pagination, and specifies the return format. The presence of an output schema further reduces the need to detail return values. No essential information 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?

Although the schema has parameters, the description adds meaningful semantics: 'limit' is the maximum number of posts, and 'cursor' is for pagination from a previous response. This goes beyond the bare schema and fully explains how to use each parameter.

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 the tool fetches the authenticated user's recent Threads posts, using a specific verb and resource. This scope distinguishes it from sibling tools like threads_get_post_details, threads_get_replies, and threads_search, which target specific posts or different query modes.

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 clearly implies it is for retrieving the current user's recent posts with pagination, but it does not explicitly exclude alternatives or mention when to prefer this over sibling tools. The context is clear enough for an agent to select it for list-recent-posts scenarios.

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