get

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read ("Fetch") and says the full text and metadata come back, but says nothing about what happens when the id is missing, whether note ids and chunk ids share a namespace, or what access is required. For a lookup tool with zero annotation coverage, that is a real gap.

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 tight sentence with the verb, the resource, the selector, and the return payload all front-loaded. No filler to trim.

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 correctly stays brief on that. However, with no annotations and a 0%-covered schema, the agent still lacks the id-format and not-found semantics needed to call this reliably rather than falling back to search.

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 (item_id) with 0% schema description coverage. The description's 'by id' tells the agent what item_id is, which partly compensates, but it does not clarify the accepted id format or whether note and chunk ids are interchangeable.

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: fetch one note or chunk, by id, returning full text and metadata. That distinguishes it from the other retrieval siblings (search, list_versions) which return collections. It doesn't name a sibling explicitly, so it stops short of a 5.

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: you call this when you already have an id and need the full payload. There is no explicit statement of when to prefer this over search, nor what to do when the id is unknown (i.e. search first). Nothing is misleading, but the agent must infer the routing.

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