delete_base

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

Discloses behavioral traits beyond the obvious deletion: respects read-only mode and performs backup-on-write. No annotations exist, so description carries full burden; it adds useful safety context.

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?

Very concise: three sentences cover purpose, behavioral notes, and parameter. No wasted words; front-loads core action.

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?

Adequate for a simple single-parameter tool with no output schema. Covers purpose, parameter meaning, and key behaviors. Could mention error handling or confirmation, but not essential given tool simplicity.

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?

Description defines 'path' as 'Vault-relative path to the .base file to delete', adding format and file type constraints. Schema has 0% coverage, so description compensates meaningfully.

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?

Description clearly states 'Delete a .base file' with a specific verb and resource. It distinguishes from siblings like delete_note by specifying '.base files' only.

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 implies usage for .base files only ('Only .base files can be deleted'), but does not explicitly provide when-to-use or alternative tools like delete_note for other file types.

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