x_post

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

No annotations are provided, so the description must carry the transparency burden. It adds the endpoint path and that the ID comes from the post URL, but it does not describe the return format, error behavior, rate limits, or side effects. For a scraping tool, the read-only nature is implied but not explicit.

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 concise sentences, front-loads the primary purpose, and wastes no words. Every sentence contributes useful information for selecting and invoking the tool.

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?

The tool is simple with one required parameter and clear schema coverage, but there is no output schema and the description does not mention what the response contains. Since the tool's purpose is scraping, the agent can infer it returns post data, but error and output behavior are unspecified. The description is adequate but not fully complete.

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 100%, with both api_key and tweetId already well described in the input schema. The description's instruction to pass the numeric tweet ID merely echoes the schema example and adds no new parameter semantics beyond what the schema provides.

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 uses a specific verb ('Scrape') and resource ('X (Twitter) post (tweet)') and names the exact endpoint (/x/post). It clearly distinguishes from siblings like x_profile, which targets profiles, and generic scrape.

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 clearly indicates that the tool is for scraping a single post and instructs the user to pass the numeric tweet ID from the URL. It does not explicitly mention alternatives or exclusions, but the context is clear enough for correct selection.

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