Create HubSpot Company

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

Annotations indicate readOnlyHint=false, confirming a write operation. The description adds value by stating 'Returns: Created company with its new record ID', clarifying the return behavior. However, it does not discuss rate limits, idempotency, or error handling, which are not critical for a simple creation tool.

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, using a bullet-style list for parameters and a dedicated 'Returns' line. Every sentence is necessary, and the structure is easy to parse.

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 tool's simplicity (one required parameter with nested object) and no output schema, the description covers purpose, key parameters, and return value. It lacks guidance on when to create versus update, but overall it is adequately complete for a basic create operation.

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 input schema has 100% description coverage for the required 'properties' object, but the tool description adds practical hints like '(recommended)' for name and example domain formats. This provides extra guidance beyond the schema. Some optional fields (phone, description) are omitted from the description, but coverage is still high.

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 'Create a new company record in HubSpot CRM.' The verb 'Create' and resource 'company record' are specific and distinguishable from sibling tools like 'hubspot_get_company' or 'hubspot_update_company'.

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 such as 'hubspot_update_company'. It does not mention prerequisites, context for creation, or situations where creation is appropriate versus updating.

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