read_multiple_notes

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose error handling (e.g., if some paths are invalid), performance characteristics (e.g., rate limits for batch reads), or output format (e.g., whether content is returned as raw text or structured data). The description adds little beyond the obvious 'read' action.

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 that front-loads the core functionality ('Read content from multiple notes simultaneously'). There is zero wasted verbiage, and every word earns its place by specifying the action, target, and key differentiator (batch operation).

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 tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'content' entails (e.g., full text, metadata), how results are structured for multiple notes, or error scenarios. Given the complexity of batch operations and lack of structured context, more completeness is needed to guide the agent effectively.

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 input schema has 100% description coverage, with the 'paths' parameter fully documented in the schema itself. The description adds no additional meaning about parameters—it doesn't clarify path format, constraints, or examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 action ('Read content') and target resource ('from multiple notes'), making the purpose immediately understandable. It distinguishes from the sibling 'read_note' by specifying 'multiple notes simultaneously', though it doesn't explicitly contrast with other read-like tools like 'search_vault' or 'list_notes'.

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. It doesn't mention when batch reading is preferable over individual 'read_note' calls, nor does it address prerequisites like note accessibility or performance considerations. The agent must infer usage from the tool name alone.

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