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

Annotations cover the safety profile (destructiveHint=true, idempotentHint=false), and the description goes well beyond them: the URL is a single-use credential, `login_link_consume_disabled`/HTTP 503 means the feature is disabled, and required permissions differ per target_page ('dns' needs admin, others need view). These are authorization and side-effect facts the agent cannot infer from the schema.

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 and scope, then error/permission caveats, then a sibling disclaimer. Dense but every sentence carries operational information; only the error-code granularity could be trimmed.

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?

An output schema exists, so return values need not be described. The description covers the scope restriction, error semantics and permission requirements, which is the important context for a credential-minting mutation. The residual gap is the undocumented non-`target_page` parameters.

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 only 17% across 6 parameters, so the description must carry weight. It usefully explains the `target_page` enum's permission implications, but says nothing about `idempotency_key`, `expires_in_minutes`, `container_id`, or `container_hash`, leaving most parameters to an undocumented 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 first sentence states a specific verb (creates), resource (one-time dashboard login URL) and the effect on `target_page`. It also explicitly disclaims a sibling role, saying it is 'Not a data tool: analytics questions are answered by get_summary / get_report', so an agent can separate it from the query_* and get_* siblings.

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 states the applicability precondition ('after setup'), a hard scope restriction ('MAIN SERVER CONTAINERS ONLY'), the failure mode on other servers (`container_pinned_to_other_server`) and the alternate path (`data.manual_handoff`). It stops just short of naming a sibling tool to call in the non-main-server case, but the routing context is unusually explicit.

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