List Notes

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the behavioral trait 'bounded note content', indicating that note content is truncated or limited. This is useful but does not cover pagination, ordering, or other behaviors. No contradiction with annotations.

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, concise sentence that is front-loaded with the verb and resource. There is no superfluous information, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity, two parameters, comprehensive annotations, and the existence of an output schema, the description provides adequate context. The only gap is the ambiguous meaning of 'bounded note content' and the unexplained limit parameter, but the overall completeness is strong for a list operation.

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 0% description coverage, so the description must compensate. It clarifies that item_key identifies the item whose child notes are listed. However, the limit parameter is not explained, and the phrase 'bounded note content' likely refers to content truncation rather than the limit, leaving ambiguity about what 'limit' controls.

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 uses the specific verb 'List' and identifies the resource as 'child notes for an item', clearly distinguishing it from sibling tools like get_annotations or list_attachments. It also adds a qualifier about 'bounded note content', which further specifies the operation.

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 clear context: it is for listing child notes of an item. It does not explicitly mention when not to use it or point to alternatives, but the context is strong enough to guide selection among siblings like add_note, update_note, and delete_note.

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