user_notes_v1_delete

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

No annotations are present, so the description bears the full transparency burden. It conveys that the operation is an HTTP DELETE and requires OAuth, but it does not disclose permanence, idempotency, not-found behavior, or the specific scope of what is deleted beyond 'notes'.

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 concise, with three short sentences and the key action front-loaded. The pointer to itad://guide/calling is additional but not excessive, though it introduces a dependency on external resources.

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 output schema and a required body whose structure is undefined in both the schema and the description, the tool cannot be correctly invoked without external guidance. The reference to itad://guide/calling acknowledges this gap but does not fill it, leaving the description incomplete for a 5-parameter delete tool.

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 baseline is 3. The description adds only '必填: body' and OAuth token sourcing, both already represented in the schema, without providing further semantics about the body structure or how to specify which notes to delete.

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 opens with '[DELETE] /user/notes/v1 - Delete notes', clearly identifying the HTTP verb, endpoint, and action. It is distinct from sibling tools like user_notes_v1_get and user_notes_v1_put, making the purpose unambiguous.

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 states required inputs ('必填: body') and authentication ('需要 OAuth Token'), which are basic usage prerequisites. However, it does not explicitly explain when to choose this delete tool over the get/put siblings or mention alternatives, aside from what the name implies.

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