list_recent_posts

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

With no annotations, the description must disclose behavior itself. It states the return format (JSON string with post fields and pagination cursors) and explains pagination semantics for after/before and the limit range. It does not explicitly state that this is a read-only operation with no side effects, but the wording strongly implies it.

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 compact and well-organized, leading with the one-line purpose, then clearly labeled Args and Returns sections. Every sentence carries useful information with no redundancy or filler.

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?

For a list operation with 3 optional parameters, the description covers the purpose, parameter semantics, and return payload. It could be more complete by noting any constraints on combining after/before or by explicitly mentioning authentication expectations, but nothing critical is missing for invoking the tool correctly.

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%, so the description is the only source of parameter meaning. It fully explains limit's range and default, and clearly defines after and before as pagination cursors for subsequent and previous pages. This adds substantial meaning beyond the bare 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 begins with a specific verb and resource: 'Fetch recent posts from the authenticated user's Threads account.' This clearly identifies the operation and distinguishes it from sibling tools that cover profile info, post details, analytics, replies, or exporting.

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 about when to choose this tool over siblings such as fetch_post_replies or export_posts. There is no 'use this when...' or 'instead of...' context, leaving the agent to infer usage solely from the name and purpose.

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