get_notes

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds meaningful output-behavior context beyond the annotations: content is HTML-stripped and not truncated, which tells the agent what form the returned note content takes.

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?

Two compact sentences with zero waste; the core action and its output guarantee are front-loaded, followed by the id-sourcing hint.

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?

An output schema exists so return values need not be explained, and the description adds the content-format guarantee plus the id-source workflow. Only the batch-size limit goes unmentioned, a minor gap for a one-parameter tool.

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% for the single note_ids parameter, so the description must compensate. It usefully explains where the ids come from (search_notes) but says nothing about the array nature or the 1-50 item bounds enforced by the schema.

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 (get full note content) with clear qualifiers (HTML stripped, not truncated). It distinguishes itself from the sibling search_notes by clarifying that this returns full content while ids come from search.

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?

Explicitly routes the agent to search_notes as the source of note_ids, giving clear context for when to use this tool. It stops short of stating when-not-to-use, but the workflow dependency is well established.

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