delete_category

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly warns that deletion cascades to all associated notes and that confirm_delete=True is required. It could add irreversibility or permission details, but the core destructive behavior is transparent.

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?

Two concise sentences with no filler. The primary destructive behavior is front-loaded, and the safety requirement is stated immediately after.

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, combined with the input schema and output schema, gives enough to call the tool: pass the category name and set confirm_delete to true. It does not state what happens when confirm_delete is false, but 'requires' strongly implies no deletion occurs, so this is only a minor gap.

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?

Schema description coverage is 0%, so the description must explain parameters. It usefully explains confirm_delete, but it never directly defines the required 'name' parameter; the reader has to infer that 'name' identifies the category from the phrase 'Delete a category.'

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 uses a specific verb and object: 'Delete a category and all its associated notes.' It clarifies the destructive scope and distinguishes this tool from the sibling delete_note_by_text, which targets individual notes.

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 clearly conveys when to use the tool: when deleting a whole category and everything tied to it. It also states a key precondition, confirm_delete=True, but does not explicitly name sibling alternatives or exclusion cases.

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