mdl_account_update_privacy

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the write/open-world nature is covered. The description usefully adds that host-configured MyDramaList authentication is required, but says nothing about what the update actually changes or whether it is reversible.

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 sentences with no filler; the core action leads and constraints follow. Minor formatting issues (double spacing) but structurally sound.

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 mutation tool with no output schema and a completely undocumented parameter, the description leaves the most important questions unanswered: what 'profile_feed' means, what the update sets, and what is returned. The auth note is a partial mitigation but the definition is not complete enough to invoke confidently.

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% and the single parameter 'profile_feed' is opaque (integer, no description). The description contributes zero parameter information, so it fails to compensate for the schema gap.

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?

States a specific verb and resource ('update privacy') scoped to the account, which distinguishes it from the read sibling mdl_account_get_privacy and from mdl_account_update_profile_info. The purpose is clear, though 'privacy' is not further qualified (what settings are toggled).

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?

'Use only for an explicit user request' gives a real when-to-use constraint and implies when-not (speculative/unprompted calls). It does not name an alternative tool or describe preconditions, so it falls short of the 5 bar.

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