ghl_contact_add_to_campaign

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

Annotations indicate non-read-only, non-destructive, non-idempotent. Description adds 'empty body' but omits side effects like duplicate handling, overwrite behavior, or required permissions. Minimal extra context beyond 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?

Extremely concise: two sentences covering the core action and request body constraint. No superfluous information.

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?

Adequate for a simple add-to-campaign operation, but lacks details on return value (no output schema), error conditions, and behavior if contact already in campaign. Missing completeness for a full understanding.

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% with basic descriptions for each parameter. Description confirms body is empty but adds no further semantic value. Baseline 3 maintained as schema already provides parameter descriptions.

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?

Clearly states it adds a contact to one specific campaign, with an empty request body. The verb 'adds' and resource 'contact to campaign' are explicit, but no direct contrast with sibling tools like remove or add to workflow.

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?

Implies usage via the verb 'adds' and mentions empty body, but does not specify when to use versus alternatives (e.g., remove from campaign, add to all campaigns). No prerequisites or exclusions.

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