getNote

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action, omitting details like error handling (e.g., behavior on missing ID), return format, or side effects. This is insufficient for a tool without annotation safety signals.

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 extremely concise with no waste, but could slightly expand to include basic return information without harming conciseness.

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?

Given no output schema, the agent lacks information on the response structure. While the tool is simple, the description does not confirm what a 'note' contains or how it fits into the domain (e.g., vs. a person or task). Minimal but not fully complete for decision-making.

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 100% (the only parameter 'id' is described as 'Note ID' in the schema). The description adds no extra parameter meaning, merely restating 'by ID'. Baseline 3 is appropriate.

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 'Get a note by ID' clearly states the verb (Get), resource (note), and method (by ID), distinguishing it from siblings like createNote, updateNote, and deleteNote, as well as other get* tools for different entities.

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 on when to use this tool versus alternatives such as list tools or search. Sibling list tools exist (e.g., listTasks, listCalls) but no listNotes is visible; however, the description does not clarify that this tool is only for a single note retrieval by ID, lacking when-not-to-use advice.

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