mdl_users_get_user_watchlist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that host-configured MyDramaList authentication is required — but says nothing about pagination, result limits, or what the upstream call returns.

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 fragments, purpose front-loaded, no filler sentences. The 'Users:' prefix and the auth note are terse, though the prefix adds little over the tool name itself.

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?

With no output schema and an opaque free-form parameter, the description needed to explain the upstream parameter shape and the return semantics. It explains neither, so an agent cannot reliably invoke the tool even though annotations cover the safety profile.

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 the single 'params' parameter, so the description carries the full burden. Saying 'params is a JSON object of upstream parameters' only restates the schema's anyOf object type and gives no accepted keys (user id, page, status filter), leaving the agent unable to construct a valid call.

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 ('get user watchlist'), which is clear on its own. However, it does not distinguish itself from close siblings like mdl_watchlist_fetch, mdl_watchlist_fetch_page, or mdl_custom_lists_get_watch_status, and it never says whose watchlist (self vs. another user) is returned.

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 when-to-use guidance, no prerequisites beyond authentication, and no mention of the sibling tools that also return watchlist data. An agent must guess whether this or mdl_watchlist_fetch is the right call.

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