hubspot_update_company

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

With no annotations, the description (just 'Update...') carries full burden for behavioral disclosure. It fails to mention any side effects, such as what happens if the company_id does not exist, whether changes are reversible, or if there are any authorization requirements. This is insufficient 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?

The description is a single, straightforward sentence with no wasted words. It is front-loaded and easy to parse, though it sacrifices detail for brevity.

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 simple structure (2 parameters, no output schema), the description is minimally adequate but omits crucial context like return behavior (e.g., whether it returns the updated company or a success status). The nested 'properties' object is not elaborated.

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 100%, and the schema already describes both parameters adequately. The description adds no extra meaning beyond what the schema provides, so score is baseline 3.

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 verb 'Update', the resource 'existing company record', and the system 'HubSpot'. It distinguishes from sibling tools like hubspot_update_contact and hubspot_update_property by specifying the target entity (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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain that this tool is for updating existing companies only, while hubspot_create_company is for creating new ones. The agent lacks context to decide correctly.

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