notes_create

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create a new note' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about permissions needed, whether creation is idempotent, rate limits, what happens on failure, or what the return value might be. For a mutation tool with zero annotation coverage, this is a critical gap.

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 extremely concise at just three words, which is appropriately front-loaded. There's no wasted language or redundancy. However, this conciseness comes at the cost of being under-specified rather than efficiently informative.

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 this is a mutation tool with no annotations, 0% schema description coverage, no output schema, and complex nested parameters, the description is completely inadequate. It doesn't explain what a 'note' means in this context, what fields are required, how associations work, or what happens after creation. The agent would have insufficient information to use this tool correctly.

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 has 2 parameters with 0% description coverage, and the description provides zero information about parameters. It doesn't mention the 'properties' object containing note content and metadata, or the 'associations' array for linking to other objects. With schema coverage at 0%, the description fails completely to compensate, leaving parameters entirely undocumented.

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' clearly states the verb ('create') and resource ('note'), making the basic purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'notes_batch_create' or specify what kind of note system this is (HubSpot CRM based on parameter names). The purpose is clear but lacks differentiation and context.

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. There are multiple sibling tools for creating notes (e.g., 'notes_batch_create'), but the description doesn't indicate whether this is for single vs. batch creation, or any prerequisites like authentication. This leaves the agent guessing about appropriate usage contexts.

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