generate_passphrase

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

The description merely restates the tool name and provides no behavioral details. With no annotations provided, the description carries the full burden, and it fails to disclose output format, default behavior, randomness guarantees, or how the parameters influence the result. It is effectively a tautology.

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 extremely short, but brevity here reflects under-specification rather than purposeful conciseness. A single sentence with no detail about behavior or parameters does not structure information effectively for an agent.

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 that the tool has 4 optional parameters, no annotations, and no output schema, the description is insufficient. It does not state what the tool returns, how the parameters combine, or how it fits into the broader toolset. The schema helps, but the description leaves critical context about invocation and results unaddressed.

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 covers 100% of the parameters with descriptions, including an enum for separator, so the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides, and a score above 3 would require the description to enrich or clarify parameter semantics.

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 states a clear verb and resource: 'Generate a passphrase.' It does not distinguish itself from the sibling tool generate_random_password, so it lacks the differentiation needed for a 5. It is clear enough for an agent to know the basic action, just without comparing to alternatives.

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?

There is no guidance about when to use this tool versus generate_random_password or any other sibling. The description provides no context, exclusions, or situational advice, leaving the agent to infer usage solely from the tool name.

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