read_note

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

No annotations are provided, so the description carries the full burden. It only says 'Read' and 'Returns: Note as dict,' which implies a read-only operation, but it does not disclose error behavior, what happens for invalid/missing UUIDs, or any side effects. For a tool with zero annotation coverage, more behavioral context is needed.

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 compact and well-structured with Args and Returns sections. Every sentence contributes necessary information, and the core purpose is front-loaded. No unnecessary detail or repetition.

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?

For a simple one-parameter read operation, the description covers the essential purpose and parameter semantics. However, with no output schema, 'Note as dict' is vague about what fields will be returned, and error behavior is not mentioned. It is adequate but has clear gaps.

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 coverage is 0%, and the schema only says note_id is a string. The description adds meaningful semantics by identifying it as a 'Note UUID string,' clarifying both the format and the semantic role of the parameter. This largely compensates for the sparse 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 clear, specific operation: 'Read a note by its UUID.' This directly identifies the resource and retrieval mechanism, and distinguishes it from search/list/create/update/delete siblings. The purpose is immediately understandable.

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 implied by the UUID parameter: you should call this when you already have a note's UUID and need the full note. However, there is no explicit guidance about when to prefer read_note over search_notes, list_notes, or get_note_history, and no exclusions are stated.

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