note_batch_resolve

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

No annotations are provided, so the description carries the full burden. It discloses the 50-id cap and that all requested notes are returned, but does not explain what happens with invalid or missing ids, whether results preserve request order, what token scope is required, or how errors are surfaced. For a batched fetch tool this is a noticable 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 one sentence, front-loaded with the core action, and adds the important 50-id bound without padding. It is appropriately concise, though it sacrifices behavioral nuance.

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 no annotations, no output schema, and 0% schema coverage, the description is too thin to fully support correct invocation. It leaves out error handling, the meaning of token, ordering behavior, and relationship to note_batch_get, making the tool incomplete for an agent encountering it among many note tools.

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 explains that ids are note identifiers and that up to 50 can be provided, but it completely omits the meaning of the required token parameter, leaving the agent without enough information to construct a correct call.

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 (fetch), the resource (multiple notes by id), and the batching behavior, making the basic purpose easy to grasp. However, it does not distinguish itself from the sibling note_batch_get, which appears to cover the same operation, so it falls short of a 5.

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 phrase 'in a single batch call' implies this tool should be used when retrieving multiple notes at once, so usage context is partially conveyed. But it provides no explicit guidance on when to prefer this over note_get or note_batch_get, and no exclusions are stated.

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