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

Adds substantial behavior beyond the annotations: it returns a browser link, no account/billing change occurs until the user completes the browser flow, new-account checks can fail before returning a link, and the browser must be signed into the correct Tailwind organization and Pinterest account. This is consistent with readOnlyHint, openWorldHint, and idempotentHint.

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 front-loaded with the triggering conditions, then explains return behavior, the accountId branch, gating, and browser prerequisites. Every sentence contributes operational context for a tool with a multi-step external flow.

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?

Complete for this tool: annotations cover safety and openness, an output schema exists, and the description still supplies the critical external-flow prerequisites and gating behavior that structured fields do not capture.

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%, and the schema already documents accountId as the Tailwind account ID from list_accounts for re-authorization and omission for adding a new account. The description reinforces that distinction but does not add much parameter meaning 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?

States a specific verb and resource: connect a Pinterest account to Tailwind. It also explicitly references list_accounts and get_account for detecting unauthorized tokenStatus, so an agent can distinguish this action from the read-only sibling tools.

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 explicit triggers: user wants to connect another Pinterest account, asks about plan account limits, or has an unauthorized tokenStatus. It also explains the accountId branch clearly: pass it to re-authorize an existing account, omit it to add a new one, and notes the admin/plan-room precheck for new accounts.

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