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

Annotations already declare readOnlyHint and openWorldHint, so safety and external-dependency behavior are covered. The description adds one genuinely useful operational fact — "Costs 1 credit" — and hints at return contents, but says nothing about failure modes for private/deleted posts or how cache_max_age affects freshness.

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?

Short and readable, but the leading "Post." is pure redundancy with the title, and the credit-cost note is stranded at the end rather than front-loaded with the usage information.

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 carry the burden of describing returns, and it partially does (like count, reply count, media). But the undocumented cache_max_age and the absence of any error/edge-case behavior for a public-post lookup leave it only minimally 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 coverage is only 50%: the url parameter is documented in the schema, but cache_max_age has no description anywhere. The description does not compensate — it never mentions URL formats, shortcode acceptance, or caching behavior, leaving half the surface undocumented.

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?

"Post." merely restates the tool name; the useful content is the second sentence, which says it returns a single public Threads post with like count, reply count, and media. That clarifies scope (one post vs. many) but never states the action verb (fetch/retrieve), so the agent must infer it from readOnlyHint.

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?

No guidance on when to use this versus threads_userPosts, threads_search, or threads_profile, all of which could plausibly return post data. The URL-shaped input is the only implicit routing signal.

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