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

With no annotations, the description carries the transparency burden. It states 'Idempotent' which is a key behavioral trait, and implies state mutation. However, it does not mention side effects, error conditions, or authentication requirements, which could be relevant for a mutation operation.

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—two short sentences—with no redundant information. It efficiently conveys the core action and a key behavioral attribute.

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 action with no output schema, the description covers the essential context: what it does and that it is idempotent. It lacks details on edge cases or required permissions, but given the simplicity, it is fairly complete. The missing parameter explanations slightly reduce completeness.

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 low (only agent has a description). The text does not explain target_id or target_type beyond mentioning the types in the action phrase, but it does not explicitly map them to parameters. The description partially compensates by listing 'note, article or comment' but fails to define these as the target_type values or clarify target_id's role.

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 (remove like) and the target (note, article, or comment), which exactly matches the tool's name and purpose. It distinguishes from the 'like' sibling tool by explicitly negating the 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 implicitly indicates when to use this tool (when you want to remove a like) and notes idempotency, which is a usage-relevant trait. However, it does not explicitly contrast with alternative tools or provide conditional guidance, though the purpose is unambiguous.

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