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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered; the description adds genuinely new behavioral context by stating the operation is a simulation in an isolated twin and never produces a usable credential. It still omits whether an existing simulated token is invalidated, required permissions, and reversibility.

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 short sentences, zero filler, with the scope (isolated twin) and the key safety fact (no usable credential) front-loaded. Every 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 an output schema, full schema coverage, and annotations present, the description only needs to add what structured fields cannot express, and it does via the simulation/no-usable-credential framing. It is slightly thin on the operational effect of a simulated rotation, but nothing essential to correct invocation is missing.

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 100% with only two parameters, both self-documenting ('service' enum, optional 'reason'), so the schema carries the semantic load. The description adds no parameter-level meaning (e.g., what 'reason' feeds or how enum values map to services), which is the expected baseline of 3.

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+resource ('rotate' a 'service token') and scopes it to 'the isolated twin', which clearly separates it from the read-oriented siblings (inspect_*, list_*, read_*). It does not explicitly name any sibling as an alternative, 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?

Usage is only implied: describing the tool as a simulation in an isolated twin signals it is for dry-run/testing rather than production rotation, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer the context but receives no routing rules.

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