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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces the read-only nature by saying 'Read'. The description adds the title-based scoping but doesn't detail error behavior or return format; however, given the simple nature of the tool and the safety annotations, this is sufficient. No contradiction is present.

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 two sentences long and entirely purposeful. It front-loads the action ('Read one note by title') and immediately provides usage context. No redundant or filler wording exists.

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?

This is a simple tool with one required parameter, a schema that fully documents that parameter, and annotations declaring safety and idempotency. The description adds essential usage guidance and distinguishes from sibling tools. The absence of an output schema is acceptable for a read operation; a small omission is not specifying what happens if the title is not found, but overall the description is adequate.

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 100% coverage for the single 'title' parameter, with a clear description: 'The note's title, as given to notes_add.' The description only repeats that the note is retrieved 'by title', adding no new semantic information beyond what the schema already provides. Baseline 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?

The description states 'Read one note by title', which is a specific verb ('Read') and resource ('note') with a clear identifier ('by title'). It also distinguishes itself from the sibling notes_list by specifying the condition when each is appropriate.

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 explicitly provides usage guidance: 'Use it when you know the title; notes_list when you do not.' This clearly states when to use this tool versus an alternative, satisfying the dimension fully.

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