esxi_certificate_manage

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds real operational context the annotations cannot: the preview-first default, the need for an exact expected_host, explicit disruption/dependency acknowledgements, and request_id-based duplicate-execution protection. The request_id dedupe does not contradict idempotentHint=false (which refers to natural idempotency without a request_id), so no contradiction is flagged.

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 dense clauses, purpose front-loaded before the workflow and safety requirements. Nothing is padding, though the compressed enumeration of actions and preconditions makes it slightly harder to parse than it needs to be.

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?

An output schema exists, so return values need not be described. For a destructive, multi-action tool with zero schema description coverage, the description covers the safety preconditions and workflow but says nothing about what distinguishes the five actions or what a failed install/ca_replace implies.

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 0% across 9 parameters, so the description must carry the load. It names expected_host, request_id, the default preview (dry_run) and gestures at the write switches and dependency acknowledgements, but the required 'action' parameter has no enum and the free-form 'arguments' object is entirely unexplained, leaving meaningful gaps.

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 specific resource (certificate management) and enumerates the concrete operations it performs (csr_create, csr_by_dn, install, ca_replace, notify_services), which maps directly to the required 'action' parameter. This clearly separates it from the other esxi_*_manage siblings, though the enumeration is a bare list rather than an explanation of each action.

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?

It gives a workflow hint — run resource_schema/get first and rely on the default preview (dry_run=true) before executing — and notes that real execution requires expected_host, write switches and dependency confirmation. However it never states when NOT to use this tool or which sibling to prefer for adjacent certificate/host tasks, so the guidance is implied rather than explicit.

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