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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context (strength guarantee, default length, and the non-persisting nature implied by contrasting with save_credential), but says nothing about character set, entropy source, or the return value, so it is useful rather than rich.

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?

Two sentences, zero filler, with the primary capability and its bounds front-loaded and the alternative workflow second. Every clause earns its place.

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 single-parameter generator with no output schema, the definition covers purpose, bounds, default, and the sibling workflow well enough to invoke correctly. The one gap is that nothing states what is returned (a plain password string) or that repeated calls yield different values, which matters slightly more given there is no output schema.

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 the description must carry the parameter meaning, and it does: it restates the 12–128 range and supplies the default of 24, which the schema does not encode. It stops short of clarifying units or the consequence of an out-of-range value, which the schema's min/max handles only by rejection.

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?

States a specific verb and resource ("Generate a strong password") plus concrete constraints (12 to 128 characters, default 24), so the agent knows exactly what the tool produces without opening the schema. It is clearly distinguishable from save_credential, which is named.

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?

Explicitly names the alternative path: use save_credential with password omitted to generate and store in one call, which tells the agent when to pick the sibling over this tool. It only implicitly covers the inverse case (call this when you need the raw value without storing), so it falls short of a full when/when-not statement.

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