linkminer_delete_favorite

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

With no annotations, the description carries the full burden. It states the removal action but does not disclose permanence, required identifiers beyond list_id, error behavior, or any side effects. The single sentence conveys only the basic action with no additional behavioral context.

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?

One sentence, front-loaded, no filler. The description is appropriately concise given the simple operation.

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 nested body/query parameters and no output schema, the description should clarify the request structure and how to target a specific link. It does not, leaving critical ambiguity. The tool may be simple, but the description is under-specified for an agent to invoke it correctly without guessing.

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 description does not explain how the link being removed is specified. While list_id is clearly described in the schema, the only other parameters are generic body/query objects. The description's mention of 'a LinkMiner link' implies an additional identifier, but the schema and description fail to clarify whether it belongs in the body or query. Schema coverage is high, but the description adds no meaningful parameter guidance.

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?

Clear and specific: 'Remove a LinkMiner link from a favorite list.' Identifies the action (remove), the resource (LinkMiner link), and the context (favorite list). Distinguished from sibling tools like linkminer_set_favorite_link (which adds) and linkminer_favorites (which lists).

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 on when to use this tool versus alternatives. Does not mention that this is for removing an individual link from a list, as opposed to deleting the entire list or managing favorites in other ways. No exclusions, prerequisites, or alternative tool references.

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