generate_password

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'secure passwords' which implies security considerations, but doesn't specify what makes them secure (e.g., cryptographically random generation, entropy levels). It also doesn't mention output format, whether passwords are stored or ephemeral, or any rate limits. The description adds minimal behavioral context beyond the basic function.

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 immediately communicates the core function. Every word earns its place: 'generate' (action), 'secure passwords' (resource), 'with customizable options' (key feature). There's no redundancy or unnecessary elaboration, making it optimally concise for this tool type.

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 password generation tool with 6 well-documented parameters but no output schema and no annotations, the description is minimally adequate. It covers the what but not the how or why - missing details about security guarantees, output format, or integration considerations. The high schema coverage compensates for some gaps, but behavioral aspects remain underspecified.

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 already documents all 6 parameters thoroughly with descriptions, defaults, and constraints. The description adds no additional parameter semantics beyond 'customizable options' - it doesn't explain parameter interactions, trade-offs, or provide examples. This meets the baseline 3 when schema coverage is high.

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 verb ('generate') and resource ('secure passwords'), specifying the tool's function. It distinguishes from siblings like 'generate_random' by focusing specifically on password generation with customizable options. However, it doesn't explicitly contrast with 'generate_slug' or other generation tools, keeping it at a 4 rather than 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?

The description provides no guidance on when to use this tool versus alternatives like 'generate_random' or 'hash_string'. There's no mention of prerequisites, typical use cases, or scenarios where other tools might be more appropriate. The phrase 'with customizable options' hints at flexibility but doesn't offer concrete usage context.

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