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

Goes well past the readOnlyHint/openWorldHint annotations: it names the data source (X's embed CDN), explains why (most durable logged-out surface), discloses that TWITTER_BEARER_TOKEN switches to the official API and adds retweet/quote/impression counts, and states the cost of 1 credit. Data-source and output-shape variability are exactly the traits an agent can't get from structured fields.

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 tight sentences, front-loaded with the resource and payload, then the sourcing/fallback behavior, then the cost. Nothing is padded; every clause carries information the agent needs.

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?

With no output schema, the description does supply the return shape (text, media, engagement, plus extra counts under bearer auth), which is the main gap it needed to fill. Minor omissions remain: behavior for private/deleted/protected posts and the meaning of `cache_max_age`.

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 only 50%: `url` is documented in the schema but `cache_max_age` is undocumented in both schema and description. The description adds no parameter meaning at all — no mention of accepted URL/id forms, no caching semantics — so it fails to compensate for the coverage gap.

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?

Specific verb+resource: "Post details. One public post with its text, media and engagement." The word "one" distinguishes it from list-style siblings like twitter_userTweets, and the payload (text, media, engagement) separates it from twitter_tweetTranscript. It never names a sibling explicitly, so it stops short of a 5.

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 bearer-token sentence implies the two operating modes but doesn't say when to pick this over twitter_tweetTranscript or twitter_userTweets. Use is inferable (single post retrieval by URL/id) rather than stated, and no exclusions or prerequisites are given beyond the cost note.

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