Api organisation issues destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that – no statement about permanence, cascade effects on related objects, permissions, or a confirmation pattern. It does not contradict the 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?

It is short, but only because it contains no content at all – a bare echo of the tool name. Brevity without information is under-specification, not conciseness.

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?

This is a destructive delete on a domain object with no output schema and a 0%-covered required parameter, so the description should carry real weight. Nothing is provided about scope, consequences, or identifier sourcing, leaving the definition incomplete for a mutation tool.

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 0% and the single required parameter 'id' is completely undocumented. The description does not say what kind of identifier it is (UUID vs. numeric) or where to obtain it, leaving the parameter entirely opaque.

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 is literally the tool identifier repeated ('api_organisation_issues_destroy'), which is a tautology rather than an explanation. An agent can infer that an organisation issue is deleted, but nothing states what an 'organisation issue' is or what distinguishes this endpoint from the ten other organisation_issues siblings.

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?

There is no guidance on when to delete versus archive, what preconditions exist, or when to prefer the update/partial_update siblings. An agent must guess entirely from the name suffix.

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