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

The annotations already declare readOnlyHint and openWorldHint, and the description supplements this by explicitly stating that no CRM records are created. It adds context about checking the customer's saved connection, though it does not describe failure modes or potential OAuth refresh side effects.

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?

A single sentence that front-loads the action, names the resource, and then states the key non-effect. Every word earns its place with no redundant phrasing.

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, zero parameters, output schema presence, and safety-related annotations, the description is nearly complete. The only notable gap is the absence of explicit guidance differentiating it from sibling tools like get_hubspot_status.

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 tool has zero parameters, so the schema fully covers inputs. The description correctly avoids inventing parameter guidance, which is appropriate for a parameterless tool.

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 uses a specific verb ('Checks') with a clear resource ('the customer's saved HubSpot OAuth connection') and explicitly contrasts it with creating CRM records. This cleanly distinguishes it from mutation-focused sibling tools like push_opportunity_to_hubspot.

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 implies this is a pre-flight verification tool and clarifies that it does not create CRM records, but it does not explicitly name any sibling alternative or state when not to use it. The intended context is reasonably clear, though exclusions are absent.

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