notes_create

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers nothing beyond the basic action. It doesn't mention whether this is a write operation (implied by 'Create'), what permissions are needed, whether it's idempotent, what happens on failure, or what the response contains. This is inadequate for a tool with complex nested parameters.

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 maximally concise with just three words that directly state the core function. There's no wasted language or unnecessary elaboration, making it efficient for initial understanding despite its limitations in other dimensions.

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 creation tool with no annotations, 0% schema description coverage, complex nested parameters, and no output schema, the description is completely inadequate. It doesn't explain what gets created, how to structure the input, what the response looks like, or any behavioral characteristics. This leaves the agent with insufficient information to use the tool effectively.

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 description provides zero information about parameters, while the schema has 0% description coverage and 2 parameters with complex nested structures. The agent would have no guidance about what 'properties' and 'associations' mean, what 'hs_note_body' represents, or how to structure the association objects. This leaves critical gaps in understanding.

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 resource ('a new note'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'notes_batch_create' or 'engagement_details_create', which would require more specific context about what type of note creation this handles.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'notes_batch_create' and 'engagement_details_create' available, there's no indication whether this is for single note creation, what prerequisites might exist, or when batch operations would be more appropriate.

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