Repost a post

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds important context: 'Real account — rate-limited,' which tells the agent this is a write action with rate limits. No contradictions with annotations.

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 sentences plus a warning emoji. Front-loaded with the action, then parameter guidance. No unnecessary words; every sentence is essential.

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?

For a simple action with no output schema and three optional parameters, the description covers how to specify the post and warns about rate limits. Lacks details on return value but sufficient given low complexity.

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 100% with parameter descriptions. The description adds the 'or' logic between url and handle+code, clarifying mutually exclusive usage. This adds modest value beyond the schema.

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?

The description clearly states 'Repost a Threads post to your followers.' It specifies the action (reposting) on a specific resource (Threads post) and distinguishes from sibling tools like reply_to_thread, quote_thread, and unlike_thread.

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 description gives clear instructions on how to identify the post (url or handle+code) and warns about rate limits with '⚠️ Real account — rate-limited.' It implies usage for reposting but does not explicitly state when not to use or alternatives like unrepost_thread.

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