contacts_create_note

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

Annotations already establish that this is a mutating operation (readOnlyHint: false) and not destructive (destructiveHint: false). The description adds no behavioral context beyond 'Create Note' — no effects, side effects, or constraints. Since annotations provide minimal safety signals and the description contributes nothing extra, this scores low.

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 ('Create Note') but this is under-specification rather than effective conciseness. It lacks any structure or meaningful content, so it does not 'earn its place' — it merely echoes the tool name without adding value.

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 six parameters, no output schema, and minimal annotations, the description is grossly incomplete. It fails to indicate what the note contains, how it relates to the contact, or any operational details. An agent cannot reliably invoke this tool correctly based on this description alone.

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 17% (only 'contactId' has a description). The description provides no explanation of parameters like 'body', 'title', 'color', 'pinned', or 'userId'. With such low schema coverage, the description must compensate but does not, leaving most parameters 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 Note' is essentially a restatement of the tool name, adding no specific verb-resource detail beyond what the name already conveys. It fails to specify that this creates a note on a contact, which is implied by the tool name and required parameter 'contactId'. This is close to a tautology, offering no differentiation from other create tools.

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?

There is no guidance on when to use this tool versus alternatives like contacts_create_task or contacts_update_note. No mention of prerequisites (e.g., contact must exist) or context for when this is appropriate. The description provides zero usage direction.

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