unlikePost

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

No annotations are provided, so the description carries the full burden. It mentions 'on behalf of the authenticated user,' which hints at authentication needs, but doesn't disclose other behavioral traits such as whether the operation is reversible, potential rate limits, error conditions, or what happens if the post isn't liked. This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for its function.

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's moderate complexity (a mutation with two parameters), no annotations, and no output schema, the description is somewhat complete but has gaps. It covers the basic action and authentication context but lacks details on behavioral aspects and output, making it adequate but not fully 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?

The schema description coverage is 100%, so the schema already documents both parameters ('user_id' and 'tweet_id') with clear descriptions. The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints, which aligns with the baseline score when schema coverage is high.

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 specific action ('Unlike') and resource ('a post'), and distinguishes it from sibling tools like 'likePost' by specifying the opposite operation. It's precise and unambiguous.

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 implies usage when a user wants to remove a like from a post, but it doesn't explicitly state when to use this tool versus alternatives (e.g., 'deletePost' for removing a post entirely) or mention prerequisites like authentication. It provides basic context but lacks detailed guidance.

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