generate_password

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

With no annotations, the description carries full responsibility for disclosing behavior. It mentions 'cryptographically secure' and 'random', implying a safe, stateless operation, but does not disclose what the tool returns (e.g., a plaintext string), potential side effects, or any restrictions. This is minimal information for an agent to predict tool behavior.

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, concise sentence that conveys the essential function without extraneous detail. It is front-loaded with the action verb and fully readable at a glance, earning full marks for efficiency.

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?

The tool is simple with one optional parameter, and the description sufficiently states its core function. However, it lacks an explanation of the return value (e.g., the generated password string) and any usage context relative to sibling tools. It is minimally viable but not richly 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?

The input schema already documents the single 'length' parameter with a default value and type. Since schema description coverage is 100%, the description adds no additional meaning. The baseline score of 3 applies because the schema carries the semantic burden effectively.

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 a specific action ('Generate') and resource ('password'), with a qualifier ('cryptographically secure') that distinguishes it from other password-related operations. Among sibling tools focused on vaults and items, this is the only password generation utility, so it is unambiguous.

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, nor does it mention any prerequisites or typical scenarios (e.g., generating a password for a login). It simply states the function, leaving the agent to infer appropriate usage from the tool name alone.

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