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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description adds real context on top: thread unrolling excludes other people's replies, Articles preserve headings/lists/links/quotes/images, a downloadUrl is produced, and there is an explicit prompt-injection warning to treat content as data not instructions. That last item is genuinely valuable behavioral guidance absent from any structured field.

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 what is returned, then thread/Article behavior, then the downloadUrl affordance, then the safety note. No filler and every sentence carries a distinct fact.

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?

An output schema exists so return values need not be enumerated, yet the description still surfaces the most agent-relevant output detail (downloadUrl for exporting). Combined with thread semantics, Article fidelity, and the injection caution, an agent has everything needed to call and consume this tool correctly.

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 67%, so the schema documents most parameters, but 'format' and 'max_chars' have no description anywhere. The description reinforces the url parameter (aliases, bare ID, thread-any-post) and thread semantics, which largely duplicate the schema rather than extending it, and it never mentions format, offset, or max_chars.

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?

States a specific verb and resource ('Fetches a public X (Twitter) post and returns it as clean Markdown') and immediately scopes the resource types it handles: single posts, self-threads, and long-form Articles. An agent knows exactly what this tool retrieves and in what shape.

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?

Gives clear conditional guidance for the downloadUrl ('share it when the user wants the post as a PDF, EPUB/Kindle or Markdown file') and clarifies thread behavior. There are no sibling tools to disambiguate against, and no explicit when-not-to-use is given, so this falls just short of a 5.

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