generate_self_signed_cert

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

With no annotations, the description carries full burden. It discloses that the tool returns a dictionary with PEM-encoded certificate and private key, which is adequate for a generation tool. However, it does not specify the key algorithm or any side effects, leaving some ambiguity.

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 concise, using an Args/Returns format that is easy to parse. It includes only essential information without redundancy. Could be slightly more concise by removing the structured format, but it is efficient overall.

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?

The description covers the return format (dict with certificate and private key), and the output schema exists to further detail return structure. For a tool with three parameters, this provides sufficient context for an agent to invoke it correctly. Missing details like key algorithm are minor.

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?

Despite a context signal of 0% schema coverage, the description provides meaningful explanations for all three parameters: common_name, organization (optional), and days_valid (default 365). This adds value beyond the schema, clarifying usage and defaults.

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 explicitly states 'Generate a self-signed X.509 certificate,' using a specific verb and resource. It clearly distinguishes this tool from siblings like generate_rsa_key or parse_certificate, which serve different purposes.

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 guidance is provided on when to use this tool versus alternatives such as generate_rsa_key or other certificate-related tools. The description lacks explicit context for selecting this tool over siblings.

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