Get Proton Pass TOTP Code

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

The description claims a non-destructive read operation ('Retrieve'), but the annotation sets destructiveHint: true, which contradicts the described behavior. This is a serious inconsistency.

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?

The description is three concise sentences, each adding value: purpose, audit-logging, and time-sensitivity. No redundancy or filler.

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 simple retrieval tool with 2 parameters and an existing output schema, the description covers the key behavioral aspects (audit, time limit) and usage hints, though it omits potential permission requirements.

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%, so the schema already fully documents both parameters. The description adds general context (time-limited, audit-logged) but no parameter-specific meaning beyond the schema.

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 title and description clearly state the verb ('Retrieve') and resource ('current TOTP/2FA code for a Proton Pass item by ID'), distinguishing it from sibling tools like pass_list and pass_search.

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 description indicates when to use (to get a TOTP code) and implies timeliness ('fetch immediately before use'), but does not explicitly compare to or exclude alternative tools like pass_get.

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