Update HubSpot Company

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

Annotations already indicate idempotent hint and non-destructive behavior. The description adds valuable context by explaining partial update semantics ('Only provided fields are changed') and specifying the return value ('Returns: Updated company record'), which is critical since no output schema exists.

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 extremely concise: one sentence for purpose, one for semantics, then Args/Returns. No redundant words; all information is front-loaded and essential.

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?

Given the lack of output schema, the description adequately states the return value. It explains partial update behavior. Missing explicit mention that the company must exist, but that is reasonably inferred. Overall sufficient for a straightforward update tool.

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?

The input schema has 100% coverage for both parameters. The description reiterates them and adds context: 'Any combination of company fields to update' clarifies that the 'properties' object expects a subset of possible fields, which is beyond the schema's listing of all fields.

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 uses a specific verb ('Update') and resource ('HubSpot company'), and includes the key behavioral constraint 'Only provided fields are changed.' This clearly distinguishes it from sibling tools like create_company or delete_company.

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 usage for updating existing companies without replacing all fields, but does not explicitly state when to avoid this tool or mention prerequisites like the company needing to exist. The 'Only provided fields' note provides context for selection.

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