ghl_contact_create_note

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

Annotations already indicate non-read-only (write) and non-destructive behavior. Description adds endpoint and OAuth scopes but does not disclose idempotency, error handling, or effects (e.g., whether note is appended or replaces existing notes).

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?

Description is very brief (3 lines) and front-loaded with the title. However, it is too sparse and could include more useful context without becoming verbose.

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?

Tool creates a note on a contact but does not describe the response format, error scenarios, or prerequisites (e.g., contact must exist). No output schema, so the description should compensate but fails to do so.

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?

Input schema has 100% description coverage for all properties, so the description adds no extra meaning to parameters beyond what the schema already provides. Baseline 3 is appropriate.

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?

Tool name and description clearly indicate 'Create Note' with endpoint details. Distinguishes from sibling tools by the verb 'create' but does not explicitly differentiate from related tools like ghl_contact_update_note or ghl_contact_get_note.

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?

Description provides no information about when to use this tool versus alternatives (e.g., ghl_contact_update_note). No prerequisites or context for use are given, leaving the agent to infer usage from the tool name alone.

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