Start Totp Setup

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

Adds real behavior beyond the annotations: the secret is not persisted until confirmation, and a specific 409 error code signals the already-enabled state. Note the mild tension with destructiveHint=true, which implies mutation while the description says nothing is saved yet — this reads as the annotation marking secret generation as sensitive rather than a genuine contradiction.

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 sentences with zero waste: return value first, safety/state model second, error condition last. Every sentence carries distinct information an agent needs before invoking.

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 no-parameter tool with no output schema, the description covers the return payload (key + otpauth URI), the persistence model, and the failure mode. It could add how long the pending key remains valid, 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?

Zero parameters, so the baseline applies; there is nothing for the description to disambiguate and it correctly says nothing about inputs.

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 outcome: returns a new TOTP key plus its otpauth:// link for QR enrollment. It clearly delineates itself from enableTotp (confirmation step) and from disableTotp in the sibling set, so an agent can route between the three TOTP tools without opening a schema.

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?

The enrollment flow order is explicit — this tool first, enableTotp to confirm — and the 409 `totp_enabled` case tells the agent when not to call it. It doesn't state what to do about an abandoned pending setup or whether calling twice invalidates the first key, so it stops short of full when/when-not coverage.

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