Create Note

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that notes are timestamped, appear in contact history, preserve newlines, and escape HTML/markdown, which are meaningful behavioral traits. It doesn't cover permissions, response format, or reversibility, but the disclosed traits give the agent important context.

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 three concise sentences that front-load the core action, then add key constraints and text-handling behavior. Every sentence earns its place with no filler or redundancy.

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?

The description covers the purpose, required parameters, and note content behavior, which is substantial for a simple create operation. It lacks return-value details or error behavior, but given the schema richness and straightforward nature of the tool, the description is adequately 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 the schema already provides full descriptions for all parameters. The description reinforces that contact_id and note are required and adds note content handling behavior, but it doesn't add new parameter-specific meaning beyond the schema. Baseline 3 is appropriate.

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 uses the specific verb 'Create' with the resource 'new note attached to a contact,' clearly distinguishing it from sibling tools like edit_note, delete_note, and get_note. It also adds that notes appear in contact history, making the tool's purpose unambiguous.

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 clearly states this tool is for creating new notes in a CRM contact context, which tells the agent when to use it. It doesn't explicitly mention alternatives or exclusions, but the context is sufficient and the verb 'create' implies this is for adding rather than editing or deleting.

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