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

Annotations already cover read-only, non-destructive behavior, and the description adds meaningful semantics: it defines what BREAKING and REMOVED mean and that the list can be filtered. It does not mention pagination or output shape, but that is a minor gap given the simple read-only nature.

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?

Two tight sentences front-load the operation and definitions, with the use-case sentence adding context rather than filler. No unnecessary detail or repetition.

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 single-optional-parameter list operation with no output schema, the description adequately explains filtering and the semantic categories returned. A fully explicit output format would improve it, but nothing blocks a correct invocation.

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 already describes the single optional api parameter with 100% coverage. The description only adds concrete examples like 'CRM' and 'Webhooks', which reinforces but does not substantially extend parameter understanding.

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 ('List') with a precise resource ('HubSpot API operations whose date-based-versioning replacement is BREAKING... or REMOVED') and defines the two categories. This clearly distinguishes it from sibling lookup tools like get_hubspot_dbv_info or lookup_hubspot_endpoint.

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?

Explicitly frames when to use it ('before starting a migration') and describes the optional API-name filter. It does not explicitly contrast with sibling tools, but the use case is clear enough that an agent can decide when to call it.

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