get_2fa_code

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a 2FA code, implying a read operation, but lacks details on security implications, rate limits, authentication requirements, or response format. This is a significant gap for a tool handling sensitive data.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly.

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 tool handling sensitive 2FA codes with no annotations and no output schema, the description is incomplete. It lacks critical details like security constraints, error handling, or return value format, leaving gaps in understanding how to use it effectively in context.

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 description coverage is 100%, so the schema fully documents both parameters (username and website). The description adds minimal value beyond the schema, as it only implies the parameters are used for login context without providing additional syntax or format details.

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 the action ('Retrieve') and resource ('current 2FA code for a username'), specifying the context ('when logging into a website'). It distinguishes from sibling tools like get_account_list (lists accounts) and get_password (retrieves passwords), though it doesn't explicitly name them for comparison.

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 mentions 'when logging into a website,' which provides some context, but it doesn't offer explicit guidance on when to use this tool versus alternatives like get_password for non-2FA logins or prerequisites. No exclusions or detailed scenarios are provided.

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