create_note

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description adds no behavioral context beyond the bare action. It does not disclose side effects, required permissions, relationships between parameters (e.g., user_id, contact_id), or the nature of the created note, so the description adds no value over the annotations.

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 short (two words) but this is under-specification rather than effective conciseness. It lacks structure and does not front-load useful information; every word is essentially a restatement of the name, leaving no room for substantive guidance.

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 tool with 8 parameters, 3 required, and no output schema, the description is severely incomplete. It fails to explain what a note is, which parameters are essential, how the note relates to users/contacts/projects, or what the response will be. The context is entirely absent.

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 only 38% (3 of 8 parameters have descriptions), yet the description offers no parameter explanations. The agent gets no help understanding required fields like event_start or subject, or optional relationships like module_id and pr_project_id, making correct invocation difficult.

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 note' directly restates the tool name (create_note) without adding any scope or distinction. It is a tautology, similar to the 'Process' example, and fails to explain what kind of note, what it is associated with, or how it differs from note-related siblings beyond the action verb.

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 like update_note, delete_note, or list_notes. There are no exclusions, prerequisites, or contextual hints about typical use cases, leaving the agent without information on tool selection.

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