get_note

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

No annotations provided, so description carries full burden. States 'Get' implying read-only access, but fails to disclose error behavior (e.g., ID not found), authorization requirements, or return structure. Minimal behavioral context provided.

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?

Extremely concise five-word sentence with zero redundancy. 'specific' distinguishes from plural sibling; 'by ID' references the parameter. Every element 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?

Adequate for a simple single-resource getter with 100% schema coverage, but gaps remain given no output schema exists. Missing error handling, return value structure, or content descriptions that would help an agent handle responses appropriately.

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% (single parameter with description 'Note ID'). Description mentions 'by ID' which aligns with the parameter, but adds no additional semantic detail about ID format ranges, validation rules, or required context beyond what the schema already documents.

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?

States clear verb ('Get') and resource ('note') with scope ('specific', 'by ID'). Distinguishes from sibling 'get_notes' by emphasizing singular retrieval via ID, though could clarify what constitutes a 'note' in this CRM context.

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?

Lacks explicit when-to-use guidance versus alternatives like 'get_notes' or search patterns. While 'by ID' implies usage when an identifier is known, it does not state when to prefer this over filtering multiple notes or searching.

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