list_posts

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

No annotations exist, so the description bears full responsibility. It discloses the non-destructive nature (listing) and pagination behavior via cursor. However, it does not mention any potential authorization requirements or rate limits; still, the baseline is adequate for a read-only list tool.

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?

Two focused sentences: first defining the function and return fields, second providing usage guidance and alternatives. Every sentence adds value with no redundant information.

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 the tool's simplicity, the description covers the purpose, parameters, return fields, pagination, and usage alternatives. No output schema is provided, but the description sufficiently explains what the response contains. All typical concerns for a list endpoint are addressed.

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 input schema already has 100% coverage with descriptions for all four parameters. The description adds no additional meaning to the parameters beyond what is in the schema, though it does indirectly mention the cursor in the response context.

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 verb 'List' and resource 'the user's posts', and specifies the return fields (id, caption, etc.). It distinguishes itself from sibling tools by directing per-platform outcomes to list_post_results or list_analytics.

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?

Explicitly states when to use: 'Use this to find a post's id before calling get_post, update_post, delete_post, or publish_post, or to review upcoming scheduled content.' Also provides exclusions: 'For per-platform delivery outcomes or metrics, prefer list_post_results or list_analytics instead.'

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