jira_component_delete

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

With no annotations, the description carries full burden. It discloses that the deletion is irreversible, requires confirmation to proceed, and provides the return format (`YAML {status: ok}`). This adequately covers behavioral traits, though minor details like rate limits or auth are omitted.

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 extremely concise: two sentences plus a one-line mirror reference. It front-loads the action and key constraints (irreversible, confirmation), with no redundant information.

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 three parameters, one required, and no output schema, the description provides essential context: deletion scope, confirmation necessity, optional reassignment, and return format. It is almost complete, though a note about references being dropped if `move_issues_to` is unset is only in schema.

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%, but the description adds value by tying `component_id` to `jira_component_list` and explaining the effect of `move_issues_to`. It reinforces the schema descriptions with practical context, earning above baseline.

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 deletes a JIRA component, identifies the source of the component ID (`jira_component_list`), and distinguishes from similar tools via the mention of optional reassignment and confirmation. It is specific and actionable.

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 gives explicit guidance on when to use the tool (requires `confirm: true` for irreversible deletion) and mentions optional reassignment. It does not explicitly list alternatives or when not to use, but the context of irreversibility and confirmation provides sufficient clarity.

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