Delete Resource

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

The description adds value beyond annotations by stating that deleting a Resource also removes any assignments to Tasks, and emphasizes that the action is permanent and cannot be undone. This complements the `destructiveHint: true` annotation with specific behavioral details.

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 moderately concise but contains redundancy, repeating 'This cannot be undone' and 'Permanently removes the specified Schedule (Legacy) records' twice. The structure is acceptable, starting with the action and side effects, but could be tightened.

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 large set of sibling tools, the description adequately identifies the tool's domain (Schedule Legacy) and provides the API endpoint. It lacks details on return values or success status, but for a delete operation this is acceptable.

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 description merely repeats that `project_id` and `id` are required, which is already documented in the input schema. With 100% schema coverage, the baseline is 3, and the description adds no additional semantic meaning beyond the schema.

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 that the tool deletes a Resource, specifically Schedule (Legacy) records, and includes the API endpoint. However, it does not explicitly differentiate from the sibling tool `delete_resource_v1_0`, which may target a different resource type.

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 mentions 'Use this to permanently delete the specified Schedule (Legacy) records' but provides no guidance on when not to use this tool or alternatives like `delete_resource_v1_0`. No explicit context for when this is the appropriate choice.

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