generate_certificate

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive. The description adds the constraint that the certificate must be signed by an existing CA, which is useful context. However, no additional behavioral traits such as side effects or prerequisites are disclosed beyond that.

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 of 10 words, front-loaded with the action and object. It is concise, clear, and contains no wasted information.

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 9-parameter certificate generation tool, the description is minimal but sufficient when combined with full schema documentation and an output schema. It covers the key prerequisite ('existing CA') and the core purpose. It lacks explicit usage guidance but is not incomplete enough to warrant a lower score.

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 documents all 9 parameters with descriptions covering 100% of the schema. The description itself adds no parameter-level detail beyond what is already in the schema, so the baseline of 3 is appropriate.

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 the action (Generate), the object (a new certificate), and the specific scope (signed by an existing CA on pfSense). This distinguishes it from create_certificate or create_certificate_authority, making the purpose 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 implies that an existing CA is required, but it does not explicitly state when to use this tool over create_certificate or renew_certificate. No alternatives are named or exclusions given.

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