Undo a repost

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

Annotations already convey the core behavioral profile: readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds useful scoping via 'your' to show only the acting account's repost is affected, but it does not go into additional edge-case behavior such as what happens when no repost exists.

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 a single, immediately scannable sentence with no filler. It front-loads the verb and the object, which is exactly what an agent needs to understand and invoke the tool.

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 mutation with two well-documented parameters, strong annotations, and no nested objects, the description is complete. The agent can determine when to call it, what it does, and which parameters to provide from the schema.

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 documents both parameters fully (uri and account), so the description does not need to add parameter detail. The description provides no extra meaning beyond what the schema already covers.

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 states a specific action ('Remove') on a specific resource ('your repost of a post'), making the tool's purpose immediately clear. It also distinguishes itself naturally from the sibling tool 'repost' by being the inverse operation.

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 intended usage is clear from context: call this when you want to undo a repost. It does not explicitly discuss alternatives or exclusions, but the inverse relationship with 'repost' makes misrouting unlikely.

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