get_note

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

Describes a read-only operation without side effects, which is appropriate for a simple read. However, no annotations are provided, and the description does not disclose error handling or permissions, but it is not misleading.

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?

Extremely concise: one sentence for purpose, then structured Args/Returns. Every sentence adds value with no redundancy.

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 single-parameter read tool with no output schema, the description covers purpose, parameter, and return value completely. No additional context needed.

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 description explains the 'path' parameter's purpose ('Path to the note file to read') beyond the schema's title-only definition. Schema description coverage is 0%, so the description carries the full burden and adds clear meaning.

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 clearly states the verb 'read' and 'return', the resource 'note contents', and how 'at the specified path'. It distinguishes from siblings like 'create_note' (write) and 'get_note_paths' (list).

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 explicit guidance on when to use vs alternatives, but the context of siblings implies this is for reading a specific note. Lacks 'when not to use' or 'use X instead for Y'.

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