Delete Instruction

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

The description emphasizes irreversibility ('cannot be undone' appears twice), aligning with the destructiveHint annotation. It does not contradict any annotations and adds value by stressing permanence beyond the annotations alone.

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 somewhat repetitive (e.g., 'cannot be undone' stated twice) and includes extraneous API endpoint information. It could be more concise while retaining clarity.

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 delete operation with two parameters and no output schema, the description adequately covers the purpose, permanence, and required parameters. It is sufficiently complete given the tool's complexity.

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 provides full coverage (100%) for both parameters with descriptions. The description merely lists the required parameters but adds no new semantics beyond what the schema already conveys.

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 the verb 'delete' and the resource 'Instruction' (Daily Log records). It distinguishes this tool from the many other delete tools in the sibling list by specifying the exact 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 advises using this tool to permanently delete Daily Log records and notes that the action cannot be undone. While it does not explicitly mention when not to use it or list alternatives, the context is clear for a delete operation.

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