hubspot_create_timeline_event

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

The annotations already signal `destructiveHint: true` and `readOnlyHint: false`, so the mutation aspect is covered externally. The description adds useful context that execution is scoped under the caller's JWT, tenant, and company via the domain-agent dispatcher, but it does not describe what changes occur in HubSpot or what side effects the action has.

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 compact and front-loaded: it states the action and routing context in two short sentences, then lists both arguments cleanly. The opening sentence partially restates the tool name, but there is no unnecessary verbosity.

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 is adequate for a dispatcher-style tool with no required parameters and an output schema, but it leaves out the domain-level meaning of a timeline event and does not clarify how to populate `inputs`. In a sibling list with many HubSpot actions, this is enough to cause confusion about when and how to invoke it.

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?

With schema description coverage at 0%, the description must compensate, and it does provide minimal semantics: `message` is a free-text objective and `inputs` is an optional JSON string. However, it does not explain what structured fields `inputs` should contain for the timeline event action, which is important for constructing a correct invocation.

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 names a specific HubSpot action (`create_timeline_event`) and states it is executed through the domain-agent dispatcher, so an agent can tell it is a HubSpot creation action. However, it never explains what a timeline event is or what effect it has, and it does not differentiate it from sibling HubSpot create 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?

No guidance is given about when to use this tool versus direct HubSpot tools such as `hubspot_create_deal` or `hubspot_emit_behavioral_event`. The routing note describes how the call is dispatched but not the conditions under which this dispatcher-style tool should be selected.

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