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

The annotations already establish readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes further by disclosing the payload shape (setup URL, OAuth/webhook instructions, test steps, troubleshooting, up to five saved contacts), the guarantee that no credentials are returned, and that it does not auto-configure HubSpot or claim an existing connection. Missing only auth-permission or rate-limit context to reach the top band.

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?

Front-loaded with the core action, then mode branches, then negative guarantees, then use cases — a logical order an agent can scan. It is a fairly dense block of prose with some overlap between the "never returns/creates" list and the closing use-case sentence, keeping it out of the 5 band.

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 2-parameter, read-only tool with no output schema, the description carries the return-content burden itself (setup URL, instructions, test steps, troubleshooting, saved contacts) and states the non-effects clearly. Nothing an agent needs to call it correctly is missing.

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 only 50%: workspaceId is documented in the schema, but playId has no description there. The description compensates by explaining the two playId modes (omitted vs. supplied) and what each returns, which meaningfully extends beyond the schema. It adds no format or UUID semantics, so not a 5.

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?

"Read setup instructions for HubSpot form signups or a generic Webhook Play" gives a concrete verb (read) and resource (setup instructions / Play setup data) plus the two supported channels. The closing sentence explicitly fences off what the tool is not (creates a Play, activates a sequence, enrolls or sends), so an agent can separate it from the mutating siblings like add_to_sequence or set_sequence_status.

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?

"Use this for connecting HubSpot/forms, testing signup intake, or diagnosing webhook setup" states clear trigger scenarios, and the playId branch (omit for creation links, pass for setup URL) tells the agent which mode to invoke. It never names a competing tool to prefer instead, so it stops short of full when/when-not/alternatives guidance.

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