mdl_custom_lists_like

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutating/external nature is partly covered. The description usefully adds the authentication requirement and the explicit-user-request caution, but does not disclose the toggle/unlike capability implied by the liked=false parameter or the fact that the operation is not idempotent.

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?

Three short, front-loaded clauses with no filler; the auth and safety constraints are stated succinctly. Slight redundancy in restating the name, but efficient overall.

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 mutating, authenticated, non-idempotent tool with 0% schema coverage and no output schema, key facts are absent: how to obtain/format list_id, that the operation toggles like/unlike, and what the agent should expect on success or failure.

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% for both parameters. The verb 'like' loosely hints at the liked boolean, but the description never explains that liked=false performs an unlike, nor gives any guidance on the list_id format (integer or alphanumeric string). With no schema text to lean on, this compensation is inadequate.

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?

"Custom Lists: like" names a verb and resource, but it essentially restates the tool name (mdl_custom_lists_like) rather than explaining what liking a custom list means. It also fails to differentiate from the many sibling 'like' tools (mdl_comments_like, mdl_feeds_like, mdl_articles_like, mdl_users_like_person) or to mention that the tool can also unlike via liked=false.

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?

It gives an explicit precondition (host-configured MyDramaList authentication) and a use constraint ("use only for an explicit user request"). What's missing is any routing to alternatives such as mdl_custom_lists_set_votes or the other like-tools, so the agent still must infer which action family to pick.

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