postit.delete

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

The description discloses the core destructive behavior (deletes a note) and adds one useful nuance: the directory survives. However, with no annotations, it omits other potentially relevant behaviors such as irreversibility, permission requirements, or response 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 a single concise sentence with a clarifying parenthetical. Every word adds value and there is 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 delete tool, the description is minimally adequate but leaves gaps in parameter semantics and usage guidance. Output schema exists, which may explain return values, but the description alone does not fully cover context.

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 has 0% description coverage and the description itself barely explains parameters. 'Name' is implied as the note identifier, and 'dir survives' gives some hint about the dir parameter, but neither is formally explained.

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 tool deletes a postit note, using a specific verb and resource. It distinguishes itself from siblings as the only delete operation, with the parenthetical clarifying scope (directory survives).

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 intended use is clear: delete a postit note. There are no alternative delete tools among siblings, so explicit alternatives are unnecessary. The parenthetical provides context about directory behavior, which helps the agent decide when to use this tool.

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