delete-check

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does not disclose any behavioral traits beyond the literal action, such as whether deletion is irreversible, whether it cascades to associated data, or whether special permissions are required. The description is minimal and leaves these important aspects unmentioned.

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, clear, front-loaded sentence with no wasted words. It conveys the essential purpose immediately and is appropriately concise for a simple delete operation.

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 simplicity of the tool (one required parameter, no output schema), the description is minimally sufficient but lacks important context such as consequences of deletion or any special behaviors. It could be more complete by noting that the deletion is destructive and possibly irreversible, making it incomplete for an unannotated 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?

The input schema already describes the 'token' parameter as 'Check token', providing 100% schema coverage. The description itself adds no additional meaning about parameters, but since the schema covers the single parameter adequately, the baseline score of 3 is appropriate.

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 'Delete a monitoring check' clearly states a specific action (delete) on a specific resource (monitoring check). It effectively distinguishes this tool from sibling tools like list-checks, get-check, create-check, and update-check by focusing on the deletion operation.

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 implies usage (use when you want to delete a monitoring check) but provides no explicit guidance on when to use it versus alternatives, nor does it mention any prerequisites or when not to use it. The verb 'delete' gives a clear context, but no explicit exclusions or alternative tool references are provided.

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