crm_create_note

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Create', implying a write operation, but gives no details on required permissions, validation behavior, whether the record must exist, or the nature of the created note. This is a significant gap for a mutation tool.

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, front-loaded sentence with zero wasted words. It efficiently communicates the core action and resource, achieving maximum conciseness. Being brief is not a flaw here; the lack of content is addressed 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?

Given 5 parameters, no annotations, and no output schema, the description is inadequate for complete invocation. It does not explain which record the note attaches to, how module and record_id relate, or what the agent can expect in the response. It only covers the basic action.

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?

Schema description coverage is 0%, yet the description provides no parameter information. It does not clarify the role of 'module', 'record_id', 'Parent_Id', or the distinction between Note_Title and Note_Content. The agent gets no help beyond the raw schema, making this nearly useless for parameter 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 a specific action ('Create') and resource ('a new note for a CRM record'), which distinguishes it from sibling tools like crm_get_notes, crm_create_task, and crm_create_event. However, it lacks specifics about the target record or module scope, so it is not as precise as the TDQS 4.3 example.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that crm_get_notes is for reading notes, or that crm_create_task/event are for other record types. The description simply states what it does, leaving the agent to infer usage context.

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