hubspot_contact_form_submissions

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

Only behavioral trait disclosed is READ-ONLY. No annotations provided, so description carries full burden. Missing details on pagination, permissions, or response format beyond that.

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?

Single sentence with no wasted words, but lacks crucial information. Concise but at the expense of completeness.

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?

Despite output schema existing, description does not explain parameters or behavior fully. Agent lacks sufficient context to invoke correctly.

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 has 0% description coverage, and the description adds no meaning to the two parameters (contact_id, limit). Agent gets no context about what they represent.

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?

Description clearly identifies the resource ('form submission events') and scope ('for a HubSpot contact'), with a '(READ-ONLY)' hint. However, the verb is implicit; it could be more explicit like 'Retrieve'.

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 on when to use this tool versus siblings (e.g., hubspot_contact_email_engagement). The READ-ONLY label implies it is safe but does not differentiate from other contact tools.

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