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

With no annotations provided, the description carries the full burden and does it well. It discloses the single-use token nature, tells the agent not to write to disk or echo the URL, describes the container_pinned_to_other_server refusal, the login_link_consume_disabled 503 when the flag is off, and the admin-permission requirement for target_page: 'dns'. This is rich, actionable behavioral context.

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 long but information-dense, with critical warnings front-loaded and no filler. The second paragraph clearly separates exclusions/alternatives. It could be lightly restructured for scannability, but every sentence earns its place given the tool's complexity.

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?

Given no annotations, 6 parameters, and a complex usage context, the description covers the main flow, error/refusal cases, feature-flag behavior, permission requirements, and security handling. The presence of an output schema reduces the need to describe return structure, and the description even mentions _request_id in structuredContent. This is complete for an agent to call correctly.

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% (container_hash is the only parameter documented in the schema). The description adds meaningful semantics for target_page (admin vs. view permission) but does not explain the purpose, constraints, or interplay of idempotency_key, container_id, auth_token, or expires_in_minutes. Since the schema leaves most parameters undocumented, the description should have compensated more.

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?

Description states a specific verb and resource: 'Create a one-time dashboard handoff URL after AI setup.' It clearly distinguishes this from analytics siblings by explicitly saying it is for 'post-install navigation only' and not for data questions. An agent can immediately tell this is a discrete authentication/handoff tool rather than a query tool.

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: 'MAIN SERVER CONTAINERS ONLY' versus manual handoff on other servers, and 'DO NOT use this tool to answer analytics or stats questions' with named alternatives (get_summary, get_report, list_containers). It also covers the feature-flag-off fallback and permission requirements, leaving no ambiguity about routing.

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