x_submit_repost

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

With no annotations, the description carries full burden but does disclose the critical behavior: publishes publicly and immediately, no draft step. It omits auth requirements and failure/duplicate handling, but the key irreversibility warning is present.

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?

Two compact sentences, no filler. The irreversible-publish warning is front-loaded and earns its place.

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 no explanation, and the description covers the essential action and irreversibility. Only the account parameter semantics and the relationship to sibling tools remain unaddressed.

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 0% for both parameters. The description clarifies 'target' as a tweet URL or id, which compensates partially, but 'account' (including its empty-string default behavior) is left entirely 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?

States a specific verb (repost) and resource (tweet, as URL or id) with the defining constraint 'no added text.' Clear enough to distinguish from x_submit_post, x_submit_reply, and x_submit_quote.

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?

Implicitly distinguishes from x_submit_quote by specifying 'no added text,' which is the key branch condition, but never names the sibling tools nor states when to prefer this over x_submit_post. Clear context, no explicit exclusions.

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