Delete worklog

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

The description goes well beyond the annotations by stating that deletion is permanent, that the logged time is gone, that Jira adds it back to the remaining estimate, and that a plan shows which entry would be destroyed. This is exactly the kind of destructive side-effect disclosure an agent needs. No contradiction with annotations.

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?

Three tight sentences: action, irreversibility warning, and prerequisite. Everything earns its place and the most critical information (permanence) is front-loaded. No fluff or repetition.

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 destructive tool with no output schema, the description covers the key behavioral facts: irreversibility, effect on the estimate, the required server flag, and the plan-before-apply contract. It could have briefly mentioned the absence of a return value or idempotency, but nothing essential for invoking it correctly is missing.

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 100%, so the baseline is 3. The description's plan/apply explanation adds context around the overall workflow, but it does not add parameter-specific semantics beyond what the schema already documents for issue, worklogId, apply, plan_id, or profile.

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 opens with a specific verb and resource: 'Permanently delete one worklog entry from an issue.' This clearly identifies the operation and distinguishes it from sibling delete tools like jira_delete_issue or jira_delete_comment by naming the exact object being deleted.

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 explains the required plan-then-apply workflow and the JIRA_ALLOW_IRREVERSIBLE=true prerequisite, including the fact that planning works without that flag. It does not explicitly name alternative tools, but the resource scope makes the appropriate context clear enough.

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