abandon_change

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

There are no annotations, and the description provides no behavioral details: no mention of irreversibility, status changes, side effects, or permissions. The description merely restates the action implied by the tool name.

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 and free of fluff, but it is too terse to be considered well-structured. A single sentence can be effective when it carries enough information, but here it only repeats the tool's name with minimal context.

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 mutation-like operation with no annotations and no output schema, the description should at least state consequences or prerequisites. It does not cover whether abandonment is reversible, how it affects related items, or what success looks like.

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?

With 0% schema coverage, the description should clarify how change_id is used, but it does not. The parameter name and schema title 'Change Id' make the intent somewhat obvious, but the description adds no meaning beyond the schema.

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 clear verb and resource: 'abandon' a 'Change Request'. This distinguishes it from siblings like merge_change or approve_change, but it does not elaborate on what abandonment means or when it applies.

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 guidance is given about when to use this tool versus rollback_change, update_change, or request_changes. The intended context is only implied by the verb 'abandon', with no explicit suggestions or exclusions.

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