probely_generate_totp

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

No annotations are provided, so the description must fully disclose behavior. It indicates the tool generates a TOTP code and returns the code plus remaining validity. It does not mention any side effects, permissions, or constraints, but for a generation tool these are minimal. The description is adequate but lacks details about algorithm defaults or edge cases.

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 two sentences long, both essential. First sentence states the core action, second gives usage context and output summary. No unnecessary words or repetition.

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?

Given the tool's simplicity (4 parameters, 1 required) and the presence of an output schema (though not shown), the description covers the basics: what it does, when to use it, and what it returns. However, the lack of parameter explanations leaves a notable gap. For a tool with zero schema coverage, the description should provide more parameter context to be fully complete.

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 0%, meaning the input schema provides no descriptions for parameters. The description only mentions 'secret' (implied from 'secret/seed'), but does not explain 'algorithm', 'digits', or 'period'. This leaves the AI agent to rely on defaults or conventions, which is insufficient for correct invocation. The description should at least briefly describe each parameter or refer to TOTP standard defaults.

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?

Description explicitly states 'Generate a TOTP code from a secret/seed', providing a specific verb and resource. It clearly distinguishes from sibling tools (none of which generate TOTP codes). The context of recording login sequences with 2FA further clarifies its purpose.

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 includes 'Use this when recording login sequences that require 2FA.', which gives clear guidance on when to use the tool. However, it does not explicitly state when not to use it or mention alternatives, but the context is sufficient for most use cases.

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