hubspot_crm_update

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

With no annotations, the description discloses key behavioral traits: partial update, leaving omitted properties unchanged, clearing with empty string, and returning the updated record. It does not cover error conditions or permissions but is transparent enough for a standard update operation.

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 four sentences, front-loaded with the core purpose, and each sentence adds necessary detail without redundancy or fluff.

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 covers core usage, partial update semantics, and return value. However, since there is no output schema, it could be more specific about the response structure, but it is sufficient for an update tool with 3 well-described parameters.

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%, so baseline is 3, but the description adds value beyond the schema by explaining how to clear properties and noting that hs_timestamp is required for engagement objects, which aids correct parameter usage.

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 'Update an existing HubSpot CRM record (partial update)' with a specific verb and resource, and distinguishes from sibling tools like hubspot_crm_create or hubspot_crm_get by emphasizing the partial update nature and applicability to all object types.

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 provides guidelines on how to use the tool (partial update, clearing properties) but does not explicitly state when to use this tool versus alternatives like batch update or upsert, leaving the agent to infer usage context.

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