hubspot.v2.update_object

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Update HubSpot Object' without any details on mutation effects, required permissions, idempotency, error handling, or rate limits. This is a total failure to inform the agent of consequences.

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 sentence, but it is underspecified rather than concise. It adds no value beyond the name, failing to earn its place. A good concise description is informative in few words; this is merely short.

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 tool's complexity (6 parameters, 5 required, multiple object types and identification methods, no output schema), the description is completely inadequate. It does not explain how to use object_type, identification_method, properties, associations, or expected response format.

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 6 parameters but only 33% have descriptions (identifier_value and output_variable_name). The description adds no parameter information whatsoever. With low schema coverage, the description should compensate but does not.

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 'Update HubSpot Object' is essentially a restatement of the tool name 'hubspot.v2.update_object'. It does not specify which object types are supported or differentiate from sibling tools like 'hubspot.v2.create_object' or 'hubspot.v2.lookup_object'. This tautology provides minimal clarity.

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 given on when to use this tool versus alternatives. Sibling tools include create, lookup, search, and get variants, but the description offers no context or exclusions. The agent has no way to determine appropriate usage.

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