generate

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

With no annotations provided, the description should compensate by disclosing behavioral traits (e.g., randomness strength, whether generation is client-side or server-side, side effects). It merely states 'secure' without elaboration, leaving the agent uninformed about important security and operational details.

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 sentence that is concise and front-loaded, with no unnecessary words or repetition. It efficiently conveys the core purpose.

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 has 9 parameters and no output schema, the description is too brief. It lacks context on return format (e.g., does it return a string?), randomness guarantees, or how the parameters interact (e.g., password vs. passphrase mode). This inadequately equips the agent to use the tool effectively.

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 each parameter well. The description does not add additional meaning beyond the schema, maintaining the baseline score.

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 'Generate a secure password or passphrase' clearly states the verb ('generate') and the resource ('password or passphrase'), and it is distinct from all sibling tools which focus on CRUD and administrative tasks, leaving no ambiguity.

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?

No explicit when-to-use or alternative guidance is provided. The purpose is obvious from the tool name and description, but the description does not indicate scenarios where this tool is preferred over others or any prerequisites.

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