create_note

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

No annotations provided, so description carries burden. Discloses Markdown default, tag limitation, and return value (launched URL). Missing behaviors: error handling, side effects (e.g., does it overwrite?), permissions, or behavior on duplicate titles.

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?

Short, front-loaded, no filler. Three sentences efficiently convey key points. Could be slightly more structured but effective.

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?

Despite no annotations and no output schema, description is insufficient for a 5-param tool. Missing prerequisites (e.g., does UpNote need to be installed?), error scenarios, and behavior for partial parameter sets. The return value is mentioned but not structured.

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 0%, so description must compensate. Explains 'content' as Markdown (linking to markdown param) and 'notebook' matches by name. No explanation for title, new_window, or details on content format beyond Markdown. Leaves 3 of 5 parameters unexplained.

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 action ('Create a new note') and resource ('in UpNote') via a specific method ('URL scheme'). It distinguishes from siblings like get_note or open_note by highlighting creation via URL, though not explicitly naming alternatives.

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?

Implies usage for creating new notes. Provides a limitation ('Tags cannot be set via the URL scheme'), guiding when not to use if tags are needed. Does not explicitly mention when to use sibling tools like search_notes or open_note.

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