HubSpot MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create a new engagement' implies a write/mutation operation, but the description doesn't mention required permissions, whether this is idempotent, what happens on failure, rate limits, or what the response contains. For a creation tool with complex nested parameters and no annotation coverage, this is a significant gap in behavioral transparency.

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 at just 5 words. It's front-loaded with the core action ('Create a new engagement') and adds a clarifying detail ('with details'). There's no wasted language or unnecessary elaboration.

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 complexity (3 parameters with nested objects, no output schema, no annotations, 0% schema description coverage), the description is completely inadequate. It doesn't explain what an 'engagement' is in this system, what fields are required beyond the schema's technical requirements, what the tool returns, or any behavioral aspects. For a creation tool with this level of complexity, the description should do much more.

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 schema has 0% description coverage, meaning none of the 3 parameters (engagement, associations, metadata) have any documentation in the schema. The description mentions 'with details' but doesn't explain what those details are, what the 'engagement' object should contain, what 'associations' means, or what 'metadata' is for. The description fails to compensate for the complete lack of schema documentation.

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 states 'Create a new engagement with details' which clearly indicates a creation operation on an engagement resource. However, it's somewhat vague about what 'engagement' means in this context and doesn't differentiate from sibling tools like 'engagement_details_update' or 'crm_create_object' that might handle similar resources.

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 guidance on when to use this tool versus alternatives. There are multiple sibling tools that create various entities (calls_create, emails_create, notes_create, tasks_create, meetings_create, crm_create_company, etc.), but the description doesn't explain when an 'engagement' is appropriate versus these other entity types or when to use this versus batch creation tools.

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