hub_sync_contact

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

With no annotations, the description is the sole source of behavioral info. It discloses that it creates/updates profiles but omits key traits: idempotency, handling of existing contacts, failure behavior (e.g., partial platform failures), rate limits, or required permissions. This is a significant gap for a mutation tool.

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?

A single sentence is efficient and front-loaded with the primary action and scope. However, it sacrifices needed detail; it's under-specified rather than genuinely concise in a helpful way. Still, the structure is tight and readable.

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 complex tool with 9 parameters, nested objects, an enum, and no output schema, the description is far too thin. It leaves out how inputs map to platforms, what success looks like, and edge cases. An agent would likely guess incorrectly about parameter usage.

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 0% — the description mentions zero parameters. It doesn't explain the purpose of contact_id, email, tags, attributes, or how they map to platform fields. With 9 params and no other documentation, the description fails to compensate.

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 states a clear verb ('Sync') and resource ('a contact') and explicitly lists target platforms, distinguishing it from siblings like hub_send_campaign or crm_create_lead. It tells the agent exactly what the tool does and its broad scope.

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?

The description implies when to use (syncing contact data across platforms) but provides no explicit guidance on when NOT to use it or how it compares to related tools like crm_create_lead or hub_send_transactional. There are no alternatives mentioned or conditions for selection.

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