generar_password_seguro

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

No annotations provided, so description must carry full burden. Mentions cryptographic security via secrets module, but does not discuss rate limits, idempotency, or side effects. Basic transparency, but could be more detailed.

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?

Short header with bullet-like parameter listing. Front-loaded purpose. Could be more concise, but overall efficient. No wasted words.

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?

Covers input parameters well and implies output (a password), but does not describe output format, error conditions, or edge cases (e.g., all flags false). Output schema exists but description doesn't leverage it.

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%, so description adds meaning. Explains each parameter (length range, boolean flags for character types) beyond schema names and defaults. Adds context like 'letras mayúsculas' and 'dígitos 0-9'.

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?

Clearly states it generates a cryptographically secure password using Python's secrets module. Distinguishes from sibling tools like 'generar_token_aleatorio' and 'verificar_fortaleza_password'.

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?

Provides parameter constraints (length range) but no explicit guidance on when to use this tool vs alternatives or when not to use it. Context is implied but not stated.

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