note_get

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

The description indicates a read-only operation but fails to disclose behavior such as what happens if no notes exist, if the item ID is invalid, or the format of the returned data. With no annotations, the description carries full burden and provides insufficient transparency.

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 concise sentence that is front-loaded with the core action. It is efficient but perhaps too terse, missing opportunities to add important details without being verbose.

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 low complexity (one parameter) but no output schema, the description is incomplete. It does not specify the return value, error handling, or the nature of 'notes', leaving significant gaps for an agent to invoke the tool correctly.

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 0% description coverage, and the description only mentions 'attached to an item id', implying that 'id' is an item ID. However, it does not explicitly state this or provide any format or constraints beyond the schema's minLength, adding minimal value.

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 the resource ('notes attached to an item id'), distinguishing it from note_add, note_update, and note_list. However, 'notes' plural may imply multiple notes but does not specify if it returns all notes or a single note, causing slight ambiguity.

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 on when to use note_get versus its siblings like note_list or note_update. There is no mention of prerequisites, context, or alternatives, leaving the agent to guess the appropriate usage.

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