pylon_delete_issue

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

No annotations are provided, and the description does not disclose behavioral traits beyond the name. For a delete operation, important details like whether the deletion is permanent, cascading, or requires special permissions are absent, leaving the agent with limited understanding of side effects.

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 sentence with no extraneous words, making it very concise. For a simple tool with one parameter, this level of conciseness is appropriate, though it lacks additional useful structure.

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 simple input schema and lack of output schema or annotations, the description should provide more context about the deletion behavior (e.g., permanent vs soft delete, error conditions). Without this, the description is incomplete for fully understanding the tool's impact.

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 'id' parameter as 'The issue ID to delete', which is 100% coverage. The description adds no additional meaning or context about the parameter, such as format, constraints, or how to obtain the ID.

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 an issue' clearly states the verb (delete) and resource (issue), making the purpose obvious. However, it does not differentiate from sibling delete tools like pylon_delete_account, which likely have similar minimal descriptions.

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 provided on when to use this tool versus alternatives, such as pylon_snooze_issue or pylon_update_issue. There is no mention of prerequisites, typical use cases, or when deletion might be inappropriate.

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