delete_change

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

No annotations are available, so the description must carry the burden. It only states the delete action without mentioning permanence, cascading effects on related change notes/tasks, permission requirements, or whether deletion is soft or hard. This is a significant gap for a destructive operation.

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 brief and front-loaded with the action statement. The parameter line is somewhat redundant but still acceptable. There is no unnecessary prose, so it is 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?

For a simple one-parameter interface with an output schema, a minimal description could suffice. However, for a delete tool, it fails to mention preconditions (e.g., whether the change must be closed), consequences (irreversibility, cascading deletion of related entities), or success/failure semantics. Given sibling tools for change notes and tasks, these aspects are relevant and unaddressed.

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%, and the description merely restates 'change_id: The change ID,' adding no meaning beyond the schema's property title 'Change Id.' It does not explain how to obtain the ID or any constraints, offering no additional guidance.

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 'Delete a change request,' with a specific verb and resource. It distinguishes itself from sibling tools like get_change_by_id, update_change, and close_change by its 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?

No explicit guidance on when to use versus alternatives is provided. The name and simple action imply it is for removing a change request, while siblings handle creation, updates, closing, and retrieval. This is implied usage, not explicit.

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