create_note

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

Annotations declare no destructive or idempotent behavior. The description adds the key behavioral trait that the note is temporary and can be archived, which goes beyond annotations. No contradiction.

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?

The description is two sentences in the first paragraph and a brief second paragraph, front-loading the core action. Every sentence adds value without waste.

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?

Given 3 parameters, no output schema, and annotations present, the description covers the purpose, temporary nature, tagging, and workflow. Missing return value info is acceptable due to no output schema. It is reasonably complete.

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%, so baseline is 3. The description mentions tagging syntax for content, which is already in the schema. It does not add substantial new meaning to the parameters beyond what the schema provides.

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' and the resource 'QuickNote in the Inbox', distinguishing it from siblings like archive_note which transforms it into a permanent Note. It specifies a specific verb and resource with scope.

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 provides clear context for use: creating temporary QuickNotes. It mentions when to use archive_note for permanent notes, but does not explicitly list alternatives among sibling tools that also create entities (e.g., create_entry).

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