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

With annotations carrying only the generic profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description adds the non-obvious traits: the link expires in 30 minutes, is single-use, connects nothing by itself, and never requires a password or token in the conversation. These are precisely the constraints an agent needs to set user expectations and avoid re-invoking or asking for secrets.

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 outcome, then usage trigger, then constraints, then safety note. The long first sentence carries a heavy parenthetical but every clause is functional. Slightly dense, not padded.

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?

No output schema exists, and the description covers what is returned (an openable link) plus its lifetime and single-use nature. For a single-required-param, non-destructive tool, 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 100% and the enum already defines the five values, so the baseline would be 3. The description goes further by explaining what the platform choice implies procedurally (Google/Meta/Business Profile = click-through OAuth; CRM/WordPress = user enters token or application password), which the enum alone does not convey.

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+resource ('Get a link the person can open to connect one platform') and disambiguates the outcome from every sibling in the list, which are all platform-action tools. The parenthetical even splits the five platforms into two distinct connection mechanics (one-click sign-in vs. self-entered token), so an agent knows exactly what it gets back.

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 trigger conditions: 'Use when a tool reports that a platform is not connected, or when asked to connect one.' That covers the two realistic invocation paths. It does not name an alternative tool or state when not to use it, but no sibling serves this purpose, so the omission is minor.

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