update_my_preferences

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

No annotations; description mentions a two-step process (prepare vs. write) but doesn't clarify what 'prepare' does without confirm=true. No disclosure of side effects, idempotency, or response.

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?

Two concise sentences, front-loaded with purpose and examples, but could be restructured for clarity on the confirmation mechanism.

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 6 optional parameters and no output schema, the description lacks detail on behavior (e.g., what happens with confirm=false, persistence, response). More context needed.

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 coverage is 0%, and description only names a few parameters (language, timezone, comment sort order) without explaining each. The confirm parameter's role is partially explained but others are missing.

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 clearly states it updates the current user's preferences (language, timezone, comment sort order), which distinguishes it from sibling tools that are all read-only.

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?

Provides guidance on when to set confirm=true or use env var to skip confirmation, but does not explicitly compare to other tools or state when not to use it.

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