Delete Issue

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

With no annotations provided, the description carries the full burden. It does disclose that the deletion is permanent, warning the agent that this action is irreversible. However, it does not elaborate on side effects, required permissions, or error behavior, leaving some uncertainty.

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 concise sentence that immediately states the action and target. Every word contributes information, and there is no redundant or vague language.

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's simplicity (one parameter, output schema present), the description is largely adequate. It confirms the permanent deletion and names the application (Panel Todo Pro), but it lacks any guidance on prerequisites or differentiation from similar tools, which would make it more complete.

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 fully describes issueId as 'Issue ID to delete' with 100% coverage. The description adds no additional information about parameter format, how to obtain the ID, or edge cases, so it does not exceed the schema 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 uses the specific verb 'permanently delete' and identifies the resource as 'an issue from Panel Todo Pro', making the operation unambiguous. It clearly distinguishes from sibling tools like panelTodo_completeIssue and panelTodo_remove, which could be confused for related but different operations.

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 does not explicitly state when to use this tool versus alternatives such as panelTodo_completeIssue or panelTodo_remove. The usage is implied by the name and description, but no alternative tools are mentioned or excluded.

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