list_social_posts

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

Lacks annotations, but description adds that it returns engagement stats. However, it does not disclose pagination, ordering, rate limits, or permissions. The statement 'published and scheduled' contradicts later mention of 'failed' status, causing minor confusion.

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?

Three sentences, efficient but front-loaded with a minor inconsistency: first sentence says 'published and scheduled' while schema and later sentence include 'failed' status. Otherwise no waste.

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 tool with output schema and full coverage of optional parameters, it covers core functionality. Missing pagination, sorting, and detailed explanation of 'engagement stats'. Siblings suggest differentiation, but not fully exploited.

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 100% with descriptions for all four parameters. Description only reinforces filtering by platform, account, or status, adding no new semantic meaning beyond the schema. The mention of 'engagement stats' relates to output, not parameters.

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?

Clearly states it lists social media posts with engagement stats, distinguishing it from siblings like create_social_post, delete_social_post, and get_social_analytics. The verb 'list' and resource 'social posts' are specific.

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?

Description implies usage for listing posts with filters and stats, but does not explicitly state when to use this tool vs alternatives (e.g., get_social_analytics) nor when not to use it. No exclusions or prerequisites mentioned.

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