get_note

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

No annotations are provided. The description states the tool performs a read operation and returns content, but it does not disclose error behavior, authorization, or whether the content is full text versus a summary. Still, 'including its content' adds some clarity beyond the tool name.

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 one short sentence, front-loaded with the verb and resource, and contains no filler or redundant wording. Every word 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?

The tool is simple with one parameter and an output schema, but the description lacks any hint about how note_id is obtained or when this tool is preferred over list_notes/search_notes. It is minimally 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 one required parameter, note_id, with 0% schema description coverage. The description does not explain note_id or its format; it only relies on the schema's title 'Note Id' and the tool's purpose.

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 uses the specific verb 'Get' with the resource 'note' and explicitly notes 'including its content,' which differentiates this from sibling list_notes/search_notes (which likely return metadata or search results). It clearly states what the tool does.

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 guidance is provided about when to choose get_note over list_notes or search_notes, and no exclusions or alternatives are mentioned. The intended usage is only implied by the name and the phrase 'including its content.'

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