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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states a create action without mentioning required fields, permissions, idempotency, side effects, or response format. This is minimal to the point of providing no useful behavioral information.

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 a single brief sentence, but it is under-specified rather than appropriately concise. It provides no additional value over the tool name and omits critical details, making it an ineffective use of the description space.

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 low complexity of a create action with 4 parameters, the description should explain what a HubSpot deal is or outline the parameter semantics. With no annotations, no output schema, and 0% schema coverage, the description is completely inadequate for an agent to select and invoke this tool 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?

The schema has 4 parameters with 0% description coverage, and the tool description adds no information about what stage, amount, dealName, or contactId mean or how they should be used. The description fails to compensate for the schema's lack of documentation, leaving parameter semantics entirely unexplained.

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 'Create a HubSpot deal' directly restates the tool name 'hubspot_create_deal' without adding any new meaning or scope. It identifies the verb and resource but is essentially a tautology, offering no differentiation from sibling tools beyond the obvious.

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 versus alternatives like hubspot_update_deal or hubspot_create_contact. No context, prerequisites, or exclusions are mentioned, leaving the agent without direction for tool selection.

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