hubspot_create_contact

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

Beyond the annotations (destructiveHint true, etc.), the description adds no information about side effects, data modifications, permissions, or consequences. It only mentions JWT/tenant/company scope for routing, which is generic and does not disclose the tool's behavioral impact.

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 concise and includes an Args section for parameters. It avoids unnecessary verbosity and is easy to scan, though it could benefit from a clearer title or a brief summary of the tool's purpose.

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 that creates a contact, the description is severely incomplete. It does not explain what constitutes a valid contact, what data the message or inputs should contain, what the expected outcome is, or any prerequisites. An agent would be unable to use this tool effectively based solely on the description.

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 description provides basic explanations for the two parameters: message is a 'free-text objective' and inputs is an 'optional JSON string of structured inputs'. This adds some meaning but remains vague—there is no detail on required fields, expected format, or how message and inputs relate. The schema already lists these parameters, so the added value is modest.

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 only says 'Run the hubspot domain agent action `create_contact`' without explaining what creating a contact entails. It is essentially tautological and doesn't clarify the tool's actual function beyond the name. No explicit distinction from similar tools like list_crm_contacts or create_crm_task is provided.

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 guidance on when to use this tool, what scenarios it applies to, or what alternatives exist. It merely describes routing through a dispatcher without any practical usage instructions. An agent would not know how to decide between this and other contact-related tools.

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