Create Note

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, which aligns with a create operation. The description adds minor context ('plain-text', 'eligible Container') but doesn't disclose side effects, permissions, or other behavioral traits beyond the annotations.

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 a single concise sentence with no fluff. However, terms like 'eligible' and 'complete' are vague and slightly undermine clarity, though overall it's well-structured and 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?

With 9 parameters and no output schema, the description is too sparse. It doesn't explain required fields, return values, or how the optional fields interact. The description alone would leave an agent under-informed about how to correctly invoke this tool.

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?

With 0% schema coverage, the description must compensate for the 9 parameters. It provides high-level groupings (Container, planning, appearance, Tag set) but omits specific parameters like in_inbox, sort_order, and planned_for_date, and doesn't clarify that body is required. This is insufficient for guiding parameter usage.

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 tool creates a plain-text Note, with optional attributes like Container, planning, appearance, and Tag set. This distinguishes it from sibling tools like personal_os_create_task or personal_os_create_tag.

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 usage by noting optional fields, but it doesn't explicitly state when to use this tool over alternatives or any exclusions. Since the tool name and description clearly indicate note creation, usage is implied rather than explicit.

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