notes.get_note

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

Description indicates a read operation ('Fetch'), but no annotations are provided. It does not disclose any potential side effects, rate limits, or data volume expectations. Adequate but minimal transparency.

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?

Single sentence with only 7 words, front-loading the action. While efficient, it could include a brief note about typical use cases without adding clutter.

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 simple retrieval nature and presence of an output schema, the description is adequate but does not explain how this tool relates to sibling tools like notes.list_notes, nor does it mention error conditions or response format.

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 100%, so each parameter already has a description. The description adds no new meaning beyond summarizing the optional flags. Baseline 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?

Description clearly states the action ('Fetch') and resource ('a note'), with optional content and attachments. This distinguishes it from sibling tools like notes.create_note, notes.update_note, and notes.list_notes, which serve different purposes.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that notes.list_note provides only summaries, or that this tool is for full details. No prerequisites or context provided.

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