hubspot_contact_journey

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

With no annotations provided, the description carries full burden. It states 'READ-ONLY' (a behavioral trait) and mentions the default limit. However, it does not disclose other behavioral aspects such as data freshness, pagination behavior, or error handling for invalid contact IDs.

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 of purpose plus a compact Args list. Every word adds value, and the most critical information is front-loaded. No unnecessary fluff.

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 presence of an output schema, the description does not need to explain return values. It covers the core function and parameter meanings. However, it could mention sorting order (e.g., chronological) or prerequisites (e.g., contact must exist) to fully guide the agent in a complex sibling context.

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 coverage is 0%, so the description must compensate. It describes 'contact_id' as 'HubSpot contact ID' and 'limit' as 'Max page visits to return (default: 50),' which adds meaning beyond the schema titles and types. However, the explanations are minimal and do not provide further constraints or format details.

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 'Get page visit history for a HubSpot contact (READ-ONLY).' It uses a specific verb ('Get') and resource ('page visit history'), distinguishing it from sibling tools like hubspot_contact_email_engagement or hubspot_contact_form_submissions.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description only notes it is READ-ONLY but does not mention context, prerequisites, or exclusions. The agent must rely on the tool name alone to differentiate among many HubSpot contact tools.

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