delete-note-resource

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

No annotations provided. Description implies a destructive action (delete) but does not disclose behavioral traits like confirmation behavior, reversibility, permissions needed, or side effects. The schema has a 'confirm' boolean, but the description doesn't explain its role.

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?

Extremely short (2 Chinese characters) but at the cost of clarity. It is under-specified rather than concisely informative.

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 no annotations, no output schema, and 4 undocumented parameters, the description is severely incomplete. An agent would struggle to use this tool correctly without external clues.

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 has 4 parameters (guid, hash, confirm, resourceGuid) with 0% description coverage. The description adds no meaning to any parameter, leaving agents to guess their purpose and format.

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?

Description '删资源' means 'delete resource', but it's vague—does not specify what kind of resource (e.g., file attachment vs. note itself). Sibling tools like 'delete-note' and 'export-note-resource' suggest it's related to note resources, but the description lacks specificity to differentiate.

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?

No guidance on when to use this tool vs. siblings like 'delete-note' or 'delete-notebook'. No context about prerequisites, alternatives, or conditions.

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