notes_batch_read

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation, implying it's non-destructive, but doesn't address critical aspects like authentication requirements, rate limits, error behavior (partial failures), response format, or pagination. For a batch operation tool, this lack of transparency 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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core functionality and appropriately sized for what it communicates, though it's arguably too brief given the tool's complexity.

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 batch read tool with 1 parameter (but complex nested structure), 0% schema description coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain the parameter semantics, return values, error handling, or how this tool differs from sibling batch operations. The agent would struggle to use this tool correctly without additional context.

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 but fails to do so. It mentions 'multiple notes' but provides no information about the 'inputs' parameter structure, required fields, optional 'properties' and 'associations' arrays, or what the enum values in associations mean. The description adds minimal value beyond what's inferred from the tool 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') with the operational context 'in a single request', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'notes_get' (single note) or 'notes_list' (list all notes), which would require explicit comparison to achieve a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'notes_get' for single notes or 'notes_list' for bulk listing. There's no mention of prerequisites, performance considerations, or error handling for batch operations, leaving the agent with insufficient context for optimal tool selection.

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