Delete note

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It clearly states the deletion is permanent, alerting users to its irreversible nature. However, it does not disclose return values, error behavior, or permission requirements, leaving some gaps 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 a single, front-loaded sentence that immediately states the verb and object. It is concise with no wasted words, and the 'by id' qualifier efficiently conveys the required input.

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?

Given the tool's simplicity (1 parameter, no output schema, no nested objects), the description fully covers the action, target, and permanence. The lack of return-value or error-handling details is a minor gap but not critical for a straightforward delete operation in the context of sibling CRUD tools.

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 schema provides a full description for the 'id' parameter ('The note id') with 100% coverage. The description's 'by id' reinforces the parameter's role but adds no new semantic information beyond the schema. Baseline 3 applies since the schema carries the burden.

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 states a specific verb ('delete'), resource ('note'), and required identifier ('by id'). It clearly distinguishes from siblings like create_note, update_note, and get_note. The word 'permanently' adds important specificity about the operation's effect.

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 when to use the tool (to remove a note) but does not explicitly state when not to use it or name alternatives like update_note or get_note. The permanence warning provides some context, but no direct comparison to sibling tools is given.

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