Read a note

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the shape of the return payload in the absence of an output schema. It does not cover behavior for an invalid or missing id, nor any pagination or size limits on large notes with many pages.

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?

A single front-loaded sentence with a colon-led payload list; every clause carries information and nothing is repeated from the schema or annotations.

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 a one-parameter schema, read-only annotations, and no output schema, the description carries the full burden of describing the return value — and it does so concretely, including the hint that page-level handwriting/drawing markers exist (implying get_page_image as the follow-up). No material gap remains for a correct call.

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?

Only one parameter, and schema description coverage is 100% — the schema already says 'Note id from list_notes.' The description adds no further semantics about the id format or lookup failure behavior, so the baseline 3 applies.

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?

States a specific verb and resource ('Read one note') and then enumerates exactly what comes back: title, folder, dates, pages, attachment list, typed text with tables, handwriting/drawing page markers. The payload enumeration implicitly distinguishes it from get_attachment (which fetches the file itself) and get_page_image (which renders a page), but no sibling is named explicitly.

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?

Usage is only implied: 'Read one note' plus the schema hint that the id comes 'from list_notes' suggests the list-then-read flow. There is no explicit statement of when to prefer this over get_page_image or notes_overview, and no exclusions or prerequisites are given.

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