delete_lists_by_id_like

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds no extra behavioral context such as authentication requirements, error behavior, or side effects beyond restating the action. It does not contradict annotations, but it also does not enrich them.

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 very short and front-loads the core action. The endpoint and argument block are concise. There is slight redundancy with the schema, but the overall structure is efficient and scannable.

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 one-parameter delete, the description is minimal but missing key context: whether authentication is required, whether only the owner can remove the like, and the exact meaning of id. It also does not differentiate from the similar user-scoped sibling endpoint. Output schema presence reduces the need for return-value details, but the gaps remain significant.

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 description coverage is 0%, so the description must compensate. It only says 'id: The id/slug of the resource,' which adds that id may be a slug but leaves 'resource' ambiguous. It should clarify that id refers to the list id/slug, not the like.

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 states a specific verb and resource: 'Remove like on a list.' The endpoint DELETE /lists/{id}/like reinforces the target. It is clear enough to distinguish from siblings like create_lists_by_id_like, though it does not explicitly name or differentiate from them.

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?

There is no guidance on when to use this tool versus alternatives. No mention of using create_lists_by_id_like to add a like, or of the related delete_users_by_id_lists_by_list_id_like variant. The usage is only implied by the action name.

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