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 mention authentication requirements, rate limits, error handling, or what happens with invalid IDs. The description is too minimal for a batch operation tool.

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 extremely concise with just 7 words, front-loading the core functionality. Every word earns its place with no redundancy or unnecessary elaboration. It's efficiently structured for a basic tool description.

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 complex nested parameters (0% schema coverage), no annotations, and no output schema, the description is severely incomplete. It doesn't explain the parameter structure, expected return format, error conditions, or performance characteristics. The minimal description is inadequate for this tool's complexity.

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 schema has 0% description coverage for its single parameter ('inputs'), which is a complex array of objects with 'id', 'properties', and 'associations' sub-parameters. The description adds no information about what these parameters mean, what format IDs should be in, what properties can be requested, or how associations work. It fails to compensate for the poor schema documentation.

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'), and specifies the operational context ('in a single request'), which distinguishes it from single-note read operations. However, it doesn't explicitly differentiate from sibling tools like 'notes_get' or 'notes_list' beyond the batch aspect.

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 listing notes with filtering). There's no mention of prerequisites, performance considerations, or trade-offs between batch and individual operations.

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