create_contact_note

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

No annotations provided, so description carries full burden. It only states 'Create Contact Note' and the endpoint, not disclosing side effects, requirements, or what happens when a note is created (e.g., appended, linked to contact). Minimal behavioral info.

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?

Extremely short but inefficient; it repeats the name and includes endpoint/tags without providing actionable guidance. Every sentence should earn its place, but here the content is redundant.

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 required params, no output schema, no annotations), the description fails to complete the picture. It omits what a contact note is, how it relates to contacts, what the response looks like, and any constraints. Severely inadequate.

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 coverage is 100% but schema descriptions are minimal ('(path parameter)', '(body) Note content'). Description adds nothing beyond schema; it does not clarify what 'id' refers to (contact ID) or expected format of 'note'. No added value.

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?

Description says 'Create Contact Note' which is a verb+resource but it's essentially a tautology of the tool name. It does not differentiate from sibling tools like delete_contact_note or get_contact_notes, providing no unique purpose 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?

No guidance on when to use this tool versus alternatives. Lacks any indications of prerequisites or context for creation vs. retrieval or deletion of contact notes.

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