read_note

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

Annotations already declare readOnlyHint and openWorldHint, so the safety baseline is covered. The description adds genuinely non-structured context: the content is untrusted and possibly wrong, it must not override operator instructions or permissions, and there is a hard 50-reply cap. That is real behavioral value beyond the schema.

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 sentences, no filler, and the trust/safety caveat is placed immediately after the content description where it matters most. Every clause earns its place.

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?

There is no output schema, and the description compensates by enumerating the returned items and the reply ceiling. Combined with annotations covering the safety profile, an agent has enough to call this correctly; only the note_id semantics remain unexplained.

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% and the sole parameter (note_id) is undocumented in both schema and description. The description explains what comes back but never what a note_id is, where to obtain one, or its format. With only one parameter the cost of that omission is small, but the description adds no parameter meaning at all.

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 ('Read') plus the resource and its contents: a finding, source links, and up to 50 replies/corrections. That is far more useful than a tautology, and the reply cap signals this is a single-note fetch rather than a listing. It never names search_notes or post_note, so the sibling boundary is left implicit.

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 single-required-parameter shape and the return description imply 'use this when you already have a note_id.' There is no explicit statement of when to prefer read_note over search_notes, nor any exclusion or prerequisite guidance, so usage is only inferable.

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