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

Annotations already establish the safety profile (read-only, idempotent, non-destructive, closed-world). The description adds genuinely new behavioral context: the operation depends on a pre-existing deep-research record and a paid/active key, and it enumerates the returned artifacts. It doesn't discuss cost, delivery timing, or failure modes for missing records, keeping it below 5.

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?

Four sentences, front-loaded with what the tool produces before the inputs and prerequisites. Every sentence carries information, though the requirements sentence could be trimmed slightly without losing meaning.

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?

With no output schema, the description carries the return-value burden and does so fully by listing all four output artifacts. Combined with the input enumeration and the preconditions, an agent has everything needed to decide whether it can call the tool and what it will receive.

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?

Schema coverage is 100% — both `company` and the `format` enum are fully documented in the schema. The description restates the same two inputs (company, hubspot or salesforce) without adding format-specific syntax or behavior, so the baseline 3 applies.

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?

States a specific verb and resource — exporting one company's deep-research record as CRM import files — and names the exact artifacts produced (companies/accounts CSV, contacts CSV, research-notes doc, import steps). No sibling tool exports anything, so the scope is unambiguous.

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?

Gives a clear precondition (an existing deep-research record) and an access requirement (active Whimbrel key, flagged as paid in the title), which tells the agent when this tool is applicable. It stops short of naming alternatives or stating when not to use it, so it falls short of a 5.

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