Delete Request note

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

No annotations are provided, so the description carries the full behavioral burden. It conveys only that the operation is destructive; it says nothing about irreversibility, whether the note can be restored (note that a restore_request sibling exists, but no restore for notes), required permissions, or what happens to related data. A mutation tool with zero annotation coverage needs considerably more.

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?

It is a single short sentence with no filler, so there is no wasted text. But this is brevity by omission rather than economical writing — the structure is fine, the content is simply absent.

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 two-parameter destructive tool with no annotations and no output schema, the description should at minimum cover irreversibility and identifier sourcing. Neither is addressed, leaving the definition too thin for confident invocation.

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% and there are two required parameters (request_id, note_id). The description does not explain what either identifier is, how to obtain them, or that note_id is scoped to request_id. With a low coverage schema, the description must compensate and does not.

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 names a specific verb (delete) and resource (request note), so an agent knows roughly what happens. However, it adds nothing beyond the tool name and title — it is effectively a restatement rather than an explanation, and it does not distinguish itself from siblings like update_request_note or delete_request_task beyond the name itself.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., update_request_note for edits, or whether a note can be recovered), and no prerequisites. The agent gets only the bare action.

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