bulk_update_notes

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

No annotations are provided, so the description carries the full burden. It discloses the limitation on permanent deletion, but does not mention atomicity, error handling for invalid note_ids, or whether updates are partial/full. More behavioral detail would improve score.

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 front-loaded with a one-sentence summary, followed by a warning and parameter descriptions. While the parameter list is somewhat lengthy, every sentence is necessary and the structure aids readability.

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 has 6 parameters, no nested objects, and an output schema exists, the description covers the core purpose, a key usage caveat, and parameter semantics. It does not describe return values, but the output schema likely handles that. Overall, it is largely complete for an experienced user.

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 input schema has 0% description coverage. The description compensates fully by listing each parameter and explaining its meaning (e.g., 'trashed: If set, trash (True) or restore (False) all notes'), adding significant value beyond the bare schema.

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 'Apply the same change(s) to multiple notes in a single sync,' which is a specific verb+resource combination. It clearly distinguishes from siblings like update_note (single note) and delete_note (single deletion).

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 explicitly says 'Does not support permanent deletion — trash notes in bulk here, then use delete_note individually once you're sure.' This provides clear guidance on when not to use this tool and recommends an alternative.

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