add_notes

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

The description discloses the return format (note IDs per note, null for failures like duplicates). No annotations exist, so the description carries the burden, but it omits details on atomicity or partial failures.

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?

Two sentences convey purpose, input format, and output; no wasted words. Front-loaded with the core action.

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 only 1 parameter and no annotations, the description adequately covers input structure and output. However, it does not explain error handling beyond duplicates or provide examples.

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 coverage is 0%, but the description fully specifies the structure of each item in the 'notes' array, including optional fields, adding essential meaning beyond the schema's generic 'additionalProperties: true'.

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 'Add many notes in one call,' using a specific verb and resource. It distinguishes itself from the sibling tool 'add_note' by emphasizing batch operation.

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 use when adding multiple notes at once via 'many notes in one call,' but does not explicitly state when not to use or mention alternatives like 'add_tags'.

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