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

Annotations declare openWorldHint=true, non-idempotent, non-destructive, but reveal nothing about the interaction model. The description adds genuinely useful behavior: the session is short-lived, it is a user-facing dashboard handoff consumed via a URL, and progress must be observed by polling rather than by a direct result. It still omits session expiry timing and failure behavior.

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 sentences, both of which earn their place: the first states what is created, the second states the required follow-up flow. The handoff mechanism is front-loaded with no filler.

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 usefully compensates by naming the connect_url field the agent must surface to the user and the polling tool for progress. Annotations cover the safety profile and the schema covers all params, so the only unaddressed item is session lifetime/failure handling, a minor gap.

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 description coverage is 100%, so the platform enum, auto_start default, and workspace_id scoping are all already documented in the schema. The description mentions connect_session.connect_url, which is a response field rather than an input, so it adds no parameter meaning beyond the structured data. 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?

The description names a specific verb and resource ("Create a short-lived dashboard handoff session") and scopes it to connecting a social account, which is distinct from the plain connect_account sibling. It never explicitly names connect_account or explains why an agent would pick this session handoff instead, so it stops short of full sibling differentiation.

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?

It gives actionable workflow guidance: open connect_session.connect_url for the user, then poll list_accounts with view=connect_session. That tells the agent exactly what to do after the call, but it offers no explicit when-not condition (e.g. when to use connect_account directly instead).

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