hubspot_update_task

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

With no annotations, the description bears full burden for behavioral disclosure. It fails to mention idempotency, partial update behavior, required permissions, or return value. The tool mutates data but provides no safety information.

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?

It is concise, using only one sentence. However, it is too terse and lacks structure to convey necessary details.

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?

For a tool with 8 parameters and no output schema, the description is inadequate. It doesn't mention which properties are updatable, whether the update is a full replacement or partial, or any prerequisites like task existence.

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 only 25%, and the high-level description adds no parameter semantics. It does not clarify the meaning or usage of parameters like 'body', 'ownerId', or enums. The schema provides enums but no explanation of their significance.

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 the verb 'Update' and resource 'task's properties', clearly indicating it modifies an existing task. However, it does not differentiate from sibling tools like hubspot_create_task or other update tools.

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 no context on when to use this tool instead of alternatives like hubspot_create_task or other update tools. It lacks usage constraints or scenarios.

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