x_post

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

No annotations are provided, so the description bears the full burden. It discloses that the tool returns public data and includes a quoted post preview when present. However, it does not mention any auth requirements, rate limits, or what 'visible metrics' specifically include. While not misleading, it leaves gaps.

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 two sentences, front-loaded with the verb 'Retrieve', and contains no filler. Every sentence adds value, making it efficient for an AI agent to parse.

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 and the lack of an output schema, the description adequately covers what is returned (author, text, visible metrics, quoted post preview). The term 'visible metrics' is somewhat vague but acceptable for a basic retrieval tool. No major gaps.

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 both parameters. The description adds behavioral context for the optional 'username' parameter, explaining that mismatched authors return a 404. This goes beyond the schema and helps the agent understand error conditions.

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 action ('Retrieve an X post') and resource, and lists the return fields (author, text, visible metrics, quoted post preview). It distinguishes the tool from siblings like x_profile_posts by focusing on single post retrieval by numeric ID.

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 implies usage for retrieving a single post by ID, and the optional username parameter adds context. However, it does not explicitly state when to use this tool versus alternatives like x_profile_posts, nor does it provide when-not or alternative guidance.

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