list_post_results

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

No annotations provided, so description carries full burden. It explains that it returns per-platform results (success or error), and that setting postId ignores status and limit. No mention of side effects or auth, but the core behavior is clearly described.

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 well-structured sentences, front-loaded with purpose, no redundant words. Every sentence adds useful context.

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?

Covers when to use, what it does, and parameter interactions. Lacks explicit return format details (e.g., structure of per-platform results), but given no output schema, it provides reasonable completeness for a tool with 3 params.

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 has 100% coverage for parameter descriptions. The description adds value by explaining the interaction between postId and other params (ignores status and limit when set) and clarifying the status enum values with examples. Adds meaning beyond 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?

Description clearly states the tool returns delivery outcomes for published or failed posts with per-platform results. It distinguishes from sibling tool list_analytics by specifying this is for delivery status, not engagement metrics, and contrasts with publish_post (use after to verify).

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 says when to use (after publish_post to verify, or when user asks why post didn't appear) and when not (for engagement metrics, use list_analytics). Also explains behavior based on whether postId is provided or omitted.

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