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

Goes well beyond the annotations (destructiveHint, idempotentHint, openWorldHint) by disclosing the auth scope, the fact that the first call changes nothing, its validation behaviour, and the summary/confirm_token contract. This is exactly the kind of behavioural context annotations cannot express for a destructive replace.

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?

Front-loads the action, then the permission, then the two-call protocol, with no filler sentences. The middle sentence is long and packs validation, return values, and the confirmation gate into one clause chain, but each clause earns its place.

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 a destructive mutation with only 33% schema coverage, the description supplies the return contract (summary + confirm_token) and the safety protocol. The remaining gap is the `values` payload format, which an agent would still have to guess.

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 33% and both required parameters (`set` and `values`) are untyped empty schemas, so the description must compensate. It implies `set` selects which vocabulary (genre/occasion/extra) and that replacement is whole-set, but gives no shape or format for `values` or the semantics of a partial vs. full replacement.

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?

Names a specific verb ('replace') and a specific resource ('one of my genre, occasion or extra sets'), which is concrete enough to distinguish it from bulk tag setters like set_profile_tags. It does not explicitly name a sibling or state the boundary against those, so it stops short of a 5.

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?

Gives strong procedural context: requires `profile:write`, is a two-call flow, and the second call must only happen after a human approves the summary. It also states a boundary (arguments a field the tool does not take are refused by name). No explicit alternative tool is named for the same job, so it is not a 5.

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