get_note

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

No annotations are provided, so the description carries the burden of disclosing behavior. 'Get' clearly indicates a read-only operation, but the description says nothing about not-found behavior, authentication, or edge cases. For a simple retrieval tool this is acceptable but not rich.

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 sentence with no filler. The key qualifier 'by its ID' is front-loaded, and the wording is appropriately sized for the tool's simplicity.

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?

With only one required parameter, low complexity, and an output schema presumably describing the return value, the description is mostly sufficient for basic invocation. However, it lacks usage alternatives and any behavior around missing or invalid note IDs, leaving it merely adequate rather than complete.

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 schema has one required parameter, note_id, and description coverage is 0%. The description only restates that the note is retrieved 'by its ID,' which adds no meaning beyond the schema's own 'Note Id' property title. It does not clarify ID format, valid values, or behavior for invalid IDs.

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 qualifies it as 'by its ID,' making it clear this is a direct single-note fetch. It does not explicitly contrast it with siblings like find or list, so it is clear but not fully differentiated.

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?

'By its ID' implies the tool should be used when the caller already knows the note identifier, but there is no explicit when/when-not guidance or mention of alternative tools. The usage context is reasonably implied for a simple get-by-id operation, but not fully articulated.

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