upnote_create_note

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

With no annotations, the description carries the burden and discloses important behaviors: default notebook ('Claude Notes'), Markdown content support, and the inability to set tags or edit existing notes. This goes well beyond a bare statement of intent, though it omits any detail about the response or whether a duplicate note is always created.

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?

Three short sentences: the first says what it does, the second gives use cases, the third captures key constraints and defaults. Every sentence earns its place and the most important behavioral facts are front-loaded.

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?

For a simple create tool with three parameters, full schema coverage, and no annotations, the description covers purpose, usage context, default value, content format, and limitations. Nothing essential is missing for an agent to invoke it 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 coverage is 100% with sensible param descriptions, and the description adds extra meaning by clarifying that content is Markdown and restating the default notebook behavior for the optional notebook parameter. This enriches the schema without redundancy.

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 ('Create a new note in UpNote') and clearly distinguishes itself from sibling tools by explicitly noting it cannot edit existing notes or set tags, unlike the search, open, and list tools in the sibling set.

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?

Provides concrete use cases ('save a summary, plan, snippet or session output') and states a key constraint ('Cannot ... edit an existing note'), implying when not to use it. Does not explicitly name alternatives but the create-vs-search/open/list distinction is clear.

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