notes_batch_read

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

No annotations are provided, so the description carries full burden. It states this is a read operation, implying it's non-destructive, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error handling, pagination, or what happens with invalid IDs. For a batch operation with complex input schema, this is a significant gap.

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 concise single sentence with zero waste. Every word earns its place: 'Read' (action), 'multiple notes' (resource), 'in a single request' (batch context). No fluff or redundant information.

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?

Incomplete for a batch operation tool with 0% schema coverage and no output schema. The description doesn't explain the complex nested input structure, what properties/associations mean, return format, error behavior, or performance characteristics. Given the schema complexity and lack of annotations/output schema, the description should do much more.

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%, so the description must compensate. It mentions 'multiple notes' which hints at the 'inputs' array parameter, but doesn't explain the structure of input objects (id, properties, associations) or their purposes. The description adds minimal value beyond what's inferable from the parameter name.

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 verb ('Read') and resource ('multiple notes'), specifying it's a batch operation ('in a single request'). It distinguishes from individual note tools like notes_get, but doesn't explicitly differentiate from other batch read tools like calls_batch_read or emails_batch_read.

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 versus alternatives like notes_get (for single notes) or notes_list (for listing notes). The description mentions batch reading but doesn't provide context about efficiency trade-offs, prerequisites, or when batch operations are preferred over individual calls.

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