Repost a post

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

The description adds meaningful behavioral detail beyond the annotations: the repost is immediately visible to followers, the API has no un-repost call, and confirmation is required. This explains why destructiveHint is true and why confirm must be enforced, which is exactly the kind of context an agent needs before invoking a permanent public action.

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?

The description is two sentences with no filler. The primary action is stated first, and the critical warning about visibility and irreversibility is placed immediately after. Every sentence earns its place and the overall structure is front-loaded.

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 tool with only one required parameter, a complete input schema, and rich annotations, this description is sufficient. It covers the action, the public consequence, the irreversibility, and the confirmation requirement. No output schema exists, but for this kind of one-shot action the description provides what an agent needs to invoke it correctly and safely.

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?

The schema already provides full descriptions for all three parameters, so the baseline applies. The description does not add meaningful per-parameter meaning beyond saying the post is 'existing'; the confirm behavior is also covered in the schema. It is adequate but does not raise the value above what the schema already provides.

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 identifies the action ('repost') and the resource ('an existing Threads post') plus the destination ('your own profile'), so an agent knows what the tool does. It is more specific than a generic verb and is distinguishable from create_post and delete_post, though it does not explicitly differentiate itself from the sibling quote_post, which is also a repost-like action.

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 context: use this when you want to share an existing post to your own profile. It also flags the important constraint that the action is immediately visible and irreversible, which helps an agent decide whether to proceed. It does not name alternative tools like quote_post or list a when-to-use/ when-not-to-use rule, but the implied usage is sufficiently clear.

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