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

The description adds meaningful behavioral context beyond the annotations: it introduces the concept of a soft delete and notes that the task stops running immediately. While the destructiveHint annotation already signals a destructive operation, the soft delete detail is extra and useful, with no contradiction.

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 tightly written in two short sentences, front-loading the core purpose and then adding the key behavioral nuance. Every word earns its place with no redundancy.

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 simple single-parameter delete tool, the description covers the essential information: what it deletes, that it's a soft delete, and that it stops immediately. The lack of output schema is acceptable for a delete operation, and annotations cover the destructive aspect. Slightly more detail on the effects of soft delete could improve it, but it's already sufficiently 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 the sole parameter 'id' as a UUID of the task, so with 100% schema coverage, the baseline is 3. The description does not add parameter-specific details, but none are needed given the schema's completeness.

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 'Delete a scheduled task' with a specific verb and resource, and further clarifies it's a soft delete that stops the task immediately. This distinguishes it from sibling delete tools like delete_message or delete_contact.

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 provides no guidance on when to use this tool versus alternatives such as neuron_toggle_task or neuron_pause_bot. It only states what it does, leaving usage decisions to the agent without explicit exclusions or alternative recommendations.

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