Add Notes Batch

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds 'stable per-item outcomes,' hinting at per-item result consistency, but does not elaborate on critical behaviors like partial failure handling, atomicity, or side effects. This provides some added context but not enough depth.

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 a single, front-loaded sentence. It contains no redundant words and conveys the core purpose efficiently.

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 complex batch tool (up to 100 items, mutable) with no output schema, the description is too sparse. It fails to mention return value structure, error handling, or whether the batch is processed atomically. The phrase 'stable per-item outcomes' is a start but leaves significant operational uncertainty.

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%, meaning the description does not explain any parameters. The schema itself has clear property names (profileId, items, fields) but lacks textual descriptions. The description adds no value to parameter understanding, and with only 2 parameters, it should at least mention the purpose of the top-level parameters.

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 clearly states the tool's function: to create multiple review-pending notes. This distinguishes it from sibling tools like add_note (single note creation) and delete_notes_batch (deletion), 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 implies batch usage via the word 'multiple' and the tool name, but it does not explicitly state when to use this tool versus alternatives. It lacks guidance such as 'use this when you need to create more than one note' or exclusions for edge cases.

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