Delete Resource

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

Beyond the destructiveHint annotation, the description adds that deleting a resource also removes assignments to tasks and that the action is permanent and cannot be undone. This provides valuable context about cascading 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 relatively concise but contains redundancy: 'permanently delete' and 'cannot be undone' are each stated twice. It could be streamlined while retaining key information.

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?

The description covers the tool's purpose, side effects (cascading deletion), permanence, and the API endpoint. It does not specify return values or error handling, but the lack of output schema and presence of annotations compensate.

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?

Both parameters are fully described in the input schema (100% coverage). The description only notes they are required, adding no new semantic meaning beyond the schema's descriptions.

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 it deletes a resource (Schedule Legacy record) and provides the specific verb 'Delete' and resource name. However, the repeated mention of 'Schedule (Legacy)' and 'Resource' could cause slight confusion if there are sibling tools for different versions.

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 specify when to use this tool versus alternative delete tools (e.g., delete_resource_project). It only says 'Use this to permanently delete the specified Schedule (Legacy) records.' No explicit contraindications or alternative suggestions are provided.

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