delete_note

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action 'delete' without any information about side effects, irreversibility, permissions, or cascading consequences. This is a significant gap for a destructive operation.

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 extremely short, but this is under-specification rather than effective conciseness. While no words are wasted, the single sentence omits necessary context about parameters, behavior, and tool selection.

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?

With two required parameters, a destructive operation, and no annotations, the description is far too sparse to give an agent enough context to invoke the tool correctly. It doesn't clarify why group_id is needed, what deletion implies for related data, or what response to expect, despite the existence of an output schema.

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 what the parameters mean. It doesn't mention note_id or group_id at all, leaving an agent to infer their roles solely from names. This is insufficient for constructing a correct call.

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 'Delete a note.' is a direct restatement of the function name delete_note, providing no new information beyond the name itself. It is clear in intent but tautological, and doesn't differentiate from related note operations like edit_note or get_note_details.

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 gives no guidance on when to use delete_note instead of other note operations (create, edit, get, list). It doesn't mention any prerequisites, contexts, or exclusions, so an agent is given no help selecting this tool over siblings.

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