get_note

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It simply states 'Retrieve a note' without revealing what happens if the key is missing, the format of the returned note, or whether the operation is read-only. This lack of detail would leave an agent uncertain about error handling and return structure.

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 a single, short sentence that is front-loaded with the action and object. It contains zero redundant words and efficiently conveys the core purpose without any filler.

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 the tool's simplicity (one parameter, read operation), the minimal description might suffice, but it is not fully complete. It lacks mention of return value, error behavior, or connection to the scratchpad context. The absence of annotations and output schema means more detail would be helpful for an agent to invoke it correctly without assumptions.

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 fully describes the single parameter 'key' with the note's key/name. The description adds no extra meaning to the parameter, so it does not surpass the baseline score of 3 for high schema coverage.

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 a specific verb 'Retrieve' and identifies the resource 'note' and its location 'scratchpad'. This clearly distinguishes it from sibling tools like set_note, list_notes, and delete_note by indicating a read operation on a specific note.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention that this fetches a single note by key while list_notes would show all notes, nor does it state any prerequisites or conditions. Users must infer usage from the name and minimal description.

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