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

Annotations only declare write-capable, non-destructive, and open-world. The description adds real behavioral context the annotations cannot carry: the budget is held during the run and released, default 2/max 10 USD, and a write scope is required. It stops short of saying where the resulting media key lives or whether it persists.

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?

One tight paragraph that front-loads what gets drawn and the output format before the cost/scope caveats. Every clause earns its place despite the parenthetical density.

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 an output schema present, return values need not be described, and the definition covers output format, cost model, scope requirement, and the reply-thread option. Minor gap: no mention of failure modes or what happens if the post is private/deleted.

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%, so the schema already documents url, theme, thread, variant, and budgetUsd. The description restates theme (dark/light), thread (draw the replied-to post), and the budget default/max without adding syntax or format detail beyond the schema; baseline 3 applies.

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 (Draw/capture) plus resource (a public x.com post) and the exact output artifact (1080px-wide PNG media key), listing the rendered elements. This clearly distinguishes it from rendering siblings like screenshot_page or render_carousel.

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?

Implies usage context (public posts, needs the write scope, free budget model) but never states when to pick this over screenshot_page or render_thumbnail. The 'Needs the write scope' line is useful gating info, yet no explicit alternatives or exclusions are given.

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