upsert_lead_profile

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

With no annotations provided, the description carries the full burden of disclosing behavior. It reveals the internal operations (upsert Company, upsert Contact, associate), idempotency, return value (IDs), and error handling (bad data recorded and reported, never silently dropped). This is comprehensive for safety and side effects.

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 three sentences, each earning its place: first sentence defines the action, second sentence emphasizes idempotency, third sentence covers error handling and return values. No redundancy or unnecessary detail.

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?

The description adequately covers purpose, safety, and error behavior, and the output schema covers return values. However, given the high parameter count (10) and zero schema descriptions, the lack of parameter guidance leaves the description incomplete for correct invocation. It is sufficient for understanding what the tool does but not for parameter selection.

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%, and the description does not explain the purpose or format of any of the 10 parameters (e.g., what employee_id, company_id, decision_maker_flag represent). The description must compensate for the lack of schema parameter descriptions, but it fails to do so, leaving the agent to guess parameter semantics from names alone.

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 clearly states the action ('Create or update one lead'), the resource ('lead in HubSpot'), and specifics that it upserts both Company and Contact and associates them. It distinguishes itself from sibling tools like 'get_lead_profile' (read-only) and 'upsert_blog_summary' (different entity).

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 explains that calling the tool twice is safe and does not duplicate, indicating idempotency. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_lead_profile for reads) or when not to use it, leaving usage context implied.

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