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

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: a fresh link fails the same way as the original if the connection itself is broken, and certain integrations return a data_backfill note that must be relayed. This is genuinely useful context that annotations alone would not provide.

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 larger than a simple one-liner, but nearly every sentence earns its place by conveying workflow or formatting rules. It is reasonably structured with summary and returns sections, though it could be tightened without losing value.

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?

The description covers the link lifecycle, retry/escalation behavior, and backfill messaging, which is strong. However, it lists connect_note in the return dict without explaining what it is or whether the agent should relay it, so a small completeness gap remains.

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 input schema already describes integration_id fully with a list of allowed values, so schema coverage is 100%. The description adds some conditional context about linkedin, gmail, and outlook return values, but it does not add necessary parameter-level semantics beyond the schema.

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 opens with a specific verb and resource: 'Generate a URL the user can click to connect a tool.' It clearly differentiates itself from nearby tools by naming get_integration_status and escalate_to_team as related but distinct actions, and states the key output (a clickable connect link).

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 gives explicit when-to-use and when-not-to-use guidance: check get_integration_status first if the user claims a service is connected, and escalate_to_team instead of re-minting links after a failed retry. It also explains how to handle multi-link backfill notes, leaving no ambiguity about the intended workflow.

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