linear_removeFromFavorites

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

Annotations already declare idempotency and non-destructiveness. The description adds context that removal applies to the 'current user's favorites', which is not in the annotations. However, it does not disclose behavior when the favorite does not exist or when both IDs are provided.

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 with no unnecessary words. It efficiently conveys the action and parameter requirement.

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 presence of an output schema and full parameter coverage, the description is largely complete. It covers the purpose and usage context. A mention of idempotency or result when favorite is missing could improve completeness, but the current level is adequate.

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 input schema already describes both parameters with 100% coverage. The description adds minimal value by implying mutual exclusivity ('Provide either favoriteId or entityId'), which is not stated in the schema, but does not enhance meaning beyond that.

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 specifies the action ('Remove'), the target (entity or favorite entry), and the scope (current user's Linear favorites). It distinguishes the tool from siblings like 'linear_addToFavorites' by indicating the opposite 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 indicates that either 'favoriteId' or 'entityId' should be provided, but does not explicitly explain when to choose one over the other. It lacks guidance on when not to use this tool or mention of alternatives for managing favorites.

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