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 fails to do so. It states 'Create a new note' which implies a write operation but doesn't specify permissions required, whether it's idempotent, rate limits, error handling, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 with a single sentence 'Create a new note', which is front-loaded and wastes no words. While this brevity contributes to under-specification, it scores high on conciseness as every word directly states the tool's action without fluff.

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 tool's complexity (2 parameters with nested objects, no output schema, no annotations), the description is completely inadequate. It doesn't explain the note's purpose, required inputs like 'hs_note_body', how associations work, or what happens after creation. For a create operation with undocumented parameters and no behavioral context, this fails to provide necessary information.

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 mentions no parameters, while the input schema has 2 parameters with 0% schema description coverage and complex nested structures. The agent must infer that 'properties' contains note content and 'associations' links to other entities, but the description provides no semantic context, leaving parameters completely undocumented beyond their schema structure.

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 restates the tool name 'notes_create' without adding specificity. It mentions the verb 'create' and resource 'note' but provides no details about what a note entails in this context or how it differs from similar tools like 'notes_batch_create' or 'engagement_details_create' in the sibling list.

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. It doesn't mention prerequisites, appropriate contexts, or compare it to sibling tools like 'notes_batch_create' for bulk operations or 'notes_update' for modifications, leaving the agent with no usage direction.

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