notes_create

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 but offers none. 'Create a new note' implies a write/mutation operation but doesn't disclose any behavioral traits: no information about permissions required, whether creation is idempotent, what happens on failure, rate limits, or what the response contains. For a mutation tool with zero annotation coverage, this is completely inadequate.

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 at just three words. While severely under-specified, it contains no wasted words and is front-loaded with the core action. Every word ('Create', 'a', 'new', 'note') contributes directly to stating the basic purpose, though that purpose is inadequately explained.

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?

Given the complexity (2 parameters with nested objects, 0% schema description coverage, no annotations, no output schema), the description is completely inadequate. For a mutation tool that creates notes with associations to other objects, the description should explain the note structure, required fields, association capabilities, and expected outcomes. The current description provides none of this necessary context.

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 despite the schema having 2 parameters with 0% description coverage and complex nested structures. The input schema shows properties like 'hs_note_body', 'hs_timestamp', 'hubspot_owner_id', and 'associations' with nested objects, but the description doesn't mention any of these, their purposes, or required formats. The description fails to compensate for the complete lack of schema descriptions.

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 'Create a new note' is a tautology that essentially restates the tool name 'notes_create' without adding meaningful specificity. It doesn't distinguish this tool from sibling tools like 'notes_batch_create' or other creation tools in the server (e.g., 'calls_create', 'emails_create'), nor does it clarify what type of note or in what context. The description provides only the most basic verb+resource pairing without any distinguishing characteristics.

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 absolutely no guidance on when to use this tool versus alternatives. There are multiple sibling creation tools (e.g., 'notes_batch_create', 'engagement_details_create') and no indication of when this single-note creation is appropriate versus batch operations or other engagement types. The description offers no context about prerequisites, limitations, or typical use cases.

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