Delete certificate

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'delete', which implies a destructive action, but does not explain side effects, required permissions, or any impact on dependent resources. A delete tool should clarify that the operation is permanent.

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 a single sentence with no filler words. It conveys the necessary information without any redundancy, making it optimally concise.

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 that the tool is destructive, has no output schema, and no annotations, the description should provide more context about the operation's safety, expected response, and any conditions. It fails to address these, leaving the agent underinformed.

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?

The input schema has a single required integer parameter 'id' with exclusiveMinimum 0. The description adds 'by ID', which aligns with the schema. Since schema description coverage is 0%, the description adds some meaning but does not explain what the ID refers to (e.g., certificate ID). This is adequate for a single obvious parameter.

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 verb 'delete' and the resource 'certificate' with the method 'by ID'. It is specific enough to distinguish from sibling delete tools that target different resources. However, it could be improved by an explicit sentence differentiating it from other certificate tools.

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. It does not mention that deletion is irreversible, any prerequisites (e.g., certificate must not be in use), or that this should be used when removing a certificate from the system.

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