npm_create_certificate

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that this triggers network calls to a CA, may wait for DNS propagation (propagation_seconds), requires DNS provider credentials, or has failure/timeout semantics. 'Request' hints at asynchronous fulfillment but nothing is stated.

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?

A single short, front-loaded sentence with no waste. Brevity is appropriate, though it comes at the cost of behavioral detail.

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?

With no annotations, no output schema, and 8 parameters, the description is too thin. It omits prerequisites (DNS provider credentials, propagation timing), the distinction between HTTP and DNS challenges, and any note on provider scope beyond Let's Encrypt.

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 100%, so the schema fully documents all 8 parameters, giving a baseline of 3. The description adds no parameter guidance beyond the schema.

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+resource: 'Request a new ... SSL certificate'. Clearly distinguishes creating from renew_certificate/list/get/delete siblings. However it narrows scope to 'Let's Encrypt' while the provider param supports 'other', so the stated purpose is narrower than the tool's actual capability.

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?

Implicitly a create operation, and sibling names like npm_renew_certificate and npm_test_http_challenge suggest alternatives, but the description offers no explicit when-to-use guidance, prerequisites, or mention of alternatives.

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