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

The description goes well beyond the annotations by explaining the idempotency key (email), the downgrade risk of lifecycleStage, the no_email error code, the degraded[] fallback behavior, and the beta status with a user spot-check caveat. These are non-obvious side effects and operational details an agent needs before calling.

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 dense but well-structured: core behavior first, then conditions, prerequisites, return contract, and risk caveat. Every sentence contributes a distinct operational fact, and there is no filler or repetition.

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?

Even though there is no output schema, the description defines the success return values (contactId, companyId, noteId, degraded[]), the key error condition, the integration prerequisite, and the beta caveat. For a mutation tool with six parameters and a nested note object, this is enough for an agent to call it correctly and set user expectations.

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 high at 83%, so the schema already documents most parameters. The description adds meaningful operational context: syncCompany depends on a real domain resolving, the note is logged on the contact's timeline, and lifecycleStage is never sent by default. leadSource and workspaceId are left to the schema, which is acceptable given the high coverage.

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 specific verb and resource: sync a single lead into the workspace's connected HubSpot portal. It further clarifies the operation by referencing the integration:crm_sync workflow node and explaining upsert, company association, and note logging, making it clearly distinct from the many sibling 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?

It gives an explicit prerequisite: a connected HubSpot integration is required, and campaignstack_connect_hubspot should be used first. It also provides a hard when-not condition (leads without an email cannot be synced) and warns against sending lifecycleStage unless explicitly provided, which helps an agent decide when and how to invoke the tool.

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