create_note

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

Annotations already declare a non-idempotent, non-destructive write, and the description adds a real operational rule on top: do not auto-retry uncertain writes, which directly reinforces idempotentHint=false. It omits permission/auth requirements and failure behavior, keeping it from a 5.

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 tight sentences with the write verb front-loaded and no filler. The Markdown parenthetical is dense but earned; nothing is redundant.

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 not be described, and annotations cover the safety profile. For a 4-required-param create tool the description is nearly complete, though it could note validation or account/folder prerequisites.

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?

At 0% schema coverage the description must carry the parameter burden, and it names all four inputs (account, folder, title, markdown) and specifies the markdown body's supported constructs (headings, lists, bold/italic, safe links). It gives no format detail for the ID fields, so it is strong but not exhaustive.

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 ('CREATE') plus resource ('one note') and enumerates the required inputs, which cleanly separates it from read_note, update_note, and the folder tools. It does not explicitly name a sibling to avoid, so it stops short of a 5.

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?

The description implies prerequisites by requiring an 'explicit account, folder, title' and instructs 'Never automatically retry an uncertain write,' but it never states when to prefer this tool over update_note or create_folder. Usage is implied rather than spelled out.

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