Delete a note by its ID in the Fastidious AI application. Use it to remove an unwanted note from a collection during natural-language note management.
Delete a note by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the note to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to state that deletion is permanent/irreversible, whether it requires specific permissions, or what side effects occur—critical omissions 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?
A single, front-loaded sentence with no wasted words. It is appropriately concise for the operation, though conciseness does not compensate for missing context.
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 destructive, one-parameter tool with no annotations and no output schema, the description omits essential behavioral context such as irreversibility and permissions. The schema covers the parameter, but the description is incomplete regarding consequences.
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 100%, so the 'id' parameter is fully documented in the schema. The description adds no syntax or format details beyond the schema, so the baseline score of 3 applies.
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?
States a specific verb ('Delete') and resource ('note') with the ID qualifier, making the operation clear. However, it does not explicitly differentiate from sibling note operations beyond the obvious verb, nor does it state scope or side effects.
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?
Provides no guidance on when to delete a note versus alternatives like update_note or move_note, nor any prerequisites or warnings. The agent must infer usage entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.