Manage Certificate

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

The description claims idempotent behavior for trust/untrust, but the annotations explicitly set idempotentHint to false, creating a contradiction. Additionally, it does not disclose other important behaviors like the need for a confirmation token for destructive actions or the effects of dryRun.

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 with two sentences covering the core purpose and a key behavioral trait. However, it could be slightly more structured or include critical information like parameter roles without becoming verbose.

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?

Given the tool has 5 parameters, is destructive, and lacks an output schema, the description is incomplete. It omits essential context such as the confirmation token flow, dry-run behavior, and effects of the remove action, leaving agents underinformed for safe invocation.

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 coverage is 100%, so the baseline is 3. The description does not add any additional meaning beyond the schema; it merely restates the action enum and idempotency, which is already implicit in the parameter descriptions.

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 tool manages certificates by removing, trusting, or untrusting. It uses specific verbs and specifies the resource (certificate), and distinguishes it from sibling tools like list_certificates or manage_user.

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 provides no guidance on when to use this tool versus alternatives (e.g., other manage_* tools). It only mentions idempotency for trust/untrust but does not specify prerequisites, exclusions, or context for use.

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