create_certificate

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

No annotations provided, so description carries full burden. It discloses behavioral difference per provider (retrieval vs creation) but omits details like side effects, idempotency, auth requirements, or potential costs.

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, front-loaded with main action, no unnecessary words. Efficient and clear.

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?

Covers key behavioral difference per provider but lacks output details, error cases, prerequisites, or idempotency. Acceptable but not complete for a provisioning tool.

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 has 50% description coverage (only provider documented). Description does not add parameter specifics; domain implied but no format or constraints mentioned. Provides some context on providers but not enough to fully compensate for the gap.

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 'Provision SSL certificate' and distinguishes behavior per provider (Porkbun vs Cloudflare), differentiating from sibling tools like check_availability and get_certificate_status.

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?

Provides provider-specific context: on Porkbun it retrieves auto-provisioned cert, on Cloudflare requires Advanced Certificate Manager. Helps agent decide when to use this tool versus alternatives, but lacks explicit when-not-to-use guidance.

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