unshare_post

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

With no annotations and a description lacking behavioral details, the tool's effects are opaque. It does not disclose idempotency, error conditions (e.g., if not shared), required permissions, or what happens to associated data.

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 short (two words) but at the cost of informativeness. It fails to provide context that could be conveyed in a slightly longer sentence, such as 'Removes a share from the specified post.'

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?

Given the tool has one parameter and an output schema, the description is insufficient. It does not explain return values, success/failure indicators, or how it integrates with related flows (e.g., sharing a post).

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% and the description adds no meaning to the sole parameter 'post_id'. The parameter name implies it's an identifier, but the description offers no constraints, format, or examples 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 'Reverse share_post.' indicates it undoes a share action, which is clear from the verb 'reverse' and the sibling tool name 'share_post'. However, it lacks specificity about what 'reverse' entails (e.g., removing a share vs. toggling).

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 guidance is provided on when to use unshare_post versus alternative tools (e.g., unlike_post or undo actions). The description does not mention prerequisites, such as the post being previously shared, or side effects.

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