create-note

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

With no annotations provided, the description must disclose behavioral traits; it only states that a note is created, which is a mutating operation. It omits any details about permissions, side effects, or return value, leaving the agent with minimal behavioral 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 a single, direct sentence that front-loads the action and resource. There is no superfluous text, making it optimally concise.

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 create operation with four scalar parameters fully described in the schema, the description covers the core purpose but lacks details on prerequisites or response format. The absence of an output schema and annotations means the agent must infer some behavior, leaving moderate gaps.

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?

The input schema provides full descriptions for all four parameters, including the mapping of notable_type 'Prospect' to 'matter'. The description adds no parameter-specific information, so the baseline of 3 applies due to complete schema coverage.

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 a specific action ('Create a note') and identifies valid attachment targets ('matter, contact, or company'), aligning with the input schema's notable_type enum. This distinguishes it from other creation tools like create-task or create-event.

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 the appropriate context: creating a note on one of three entity types. It doesn't explicitly name alternatives or exclusion criteria, but the purpose is unambiguous enough for an agent to select it when a note needs to be created.

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