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

Annotations already declare the safety profile (readOnlyHint=false write, destructiveHint=false, idempotentHint=false), so the bar is lower. The description adds that it returns the saved note and that tags/notebook are optional, but discloses nothing about permissions, side effects, or how notes are stored. Adequate 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?

Two sentences with zero waste: the use case is front-loaded, then the alternative routing. Every clause 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?

An output schema exists so return values need no explanation, and annotations carry the safety profile. The description supplies the trigger, the scope (idea/snippet/jottings), and the sibling routing, which is everything an agent needs to call this simple create 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?

Schema description coverage is 50% (only title and content are documented). The description says 'optional tags and notebook', which confirms optionality for the two undocumented parameters, but that is largely implied by the required list and it adds no detail on tag format or how a notebook is chosen. Thin compensation for the coverage gap.

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 a specific verb and resource ('save something as a note'), enumerates the content kinds (idea, snippet, meeting jottings), and explicitly names the sibling it is not (create_document) for long structured pieces. An agent can distinguish it from add_to_knowledge, meeting_notes, and search_notes without opening schemas.

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?

Gives an explicit trigger ('Use this when the user wants to save something as a note') plus a named alternative and the condition that selects it ('For a long structured piece, use create_document instead'). This is the when/when-not/alternative pattern done fully.

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