Repost a Thread

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

Annotations indicate a mutation (readOnlyHint=false) but not destructive. The description adds little beyond stating it's a share action; it does not disclose behavioral traits like permissions needed, rate limits, or potential side effects like duplicate shares. With minimal annotations, the description should provide more context.

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 extremely concise: one sentence for the purpose followed by two bullet points for arguments. No extraneous words, well front-loaded with the core action.

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 two required parameters and no output schema, the description covers the basic action. However, it lacks detail on error conditions (e.g., invalid media ID, permission failures) and does not explain the response format parameter, which is only documented in the schema. It is minimally adequate but not comprehensive.

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 67% (media_id and response_format have descriptions; threads_user_id lacks one). The tool description adds the missing description for threads_user_id ('Your Threads user ID'), compensating slightly. However, it does not explain the relationship between parameters or provide additional constraints, so only marginal value added.

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 the action 'Reposts (shares) an existing thread to your profile' with a specific verb and resource. It distinguishes from sibling publishing tools that create new content rather than sharing existing threads.

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?

No explicit guidance on when to use this tool versus alternatives like threads_publish_text. The description does not mention when not to use or any prerequisites such as ownership or permissions required to repost.

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