create_inbox_note

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

The description carries the full behavioral burden because no annotations are provided. It discloses the important non-overwrite guarantee, but does not explain what happens on a filename collision (error, no-op, rename), or whether permissions or directory creation are required. This is partial transparency.

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?

A single concise sentence with the operation and scope front-loaded. The non-overwrite safety warning earns its place as critical behavioral information. No filler.

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 three-required-parameter create tool with no output schema, the description covers the core action and folder enumeration but omits conflict handling behavior and content/filename expectations. Since the 'never overwrites' statement immediately raises the collision question, some explicit error/return behavior is missing.

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 has no descriptions for the three required parameters (0% coverage), so the description must compensate. It adds useful semantics for the folder parameter by limiting values to Web/Conversations/Files, but content and filename are left to inference from the parameter names. No format or constraints are provided.

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') and resource ('a note') with the location ('inbox directory') and enumerates the possible directories (Web/Conversations/Files). This clearly separates it from sibling tools that read, list, move, search, append, update, or archive notes.

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?

Does not name alternative tools or give explicit when-to-use versus when-not-to conditions. The clause 'Never overwrites an existing file' implies it is for new notes rather than modifying existing ones, but doesn't explicitly route to append_note, move_note, or other siblings.

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