linear_removeFromFavorites

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

With no annotations, the description must convey behavioral traits fully. It states the mutation ('Remove') but does not disclose prerequisites, error conditions, side effects, or whether the operation is reversible. This is minimal transparency.

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 sentence of 17 words, no fluff, and directly conveys the purpose and parameter usage. Efficient and front-loaded.

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 removal tool with two optional params and no output schema, the description covers the core action and parameter guidance. However, it lacks context on error handling, return behavior, or prerequisites, leaving some gaps.

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?

Although schema coverage is 100%, the description adds value by indicating mutual exclusivity ('Provide either...'), which is not stated in the schema where both parameters are optional. This helps the agent choose correctly.

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') and the target ('entity or favorite entry from the current user's Linear favorites'). This distinguishes it from the sibling tool 'linear_addToFavorites' by indicating the reverse 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 description says 'Provide either favoriteId or entityId' but does not explain when to use each ID type, nor does it mention when not to use this tool or provide alternative approaches. No usage context is given.

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