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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious context beyond them: the demo is shared, it resets, and messages sent from it never reach real customers — a critical caveat an agent would otherwise not know.

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, front-loaded with what the tool yields, followed by the caveat about shared/resetting demo state. Dense but every clause carries information; the parenthetical credential list is slightly clunky but not wasteful.

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 parameters and no output schema, the description must explain what comes back, and it does: per-industry demo website and shared login credentials plus the reset/isolation caveat. Minor ambiguity remains about whether it returns one demo or all industries at once, but an agent has enough to call it 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?

Zero parameters, which sets the baseline of 4. The only parameter-like content — company ID, email, password — is clarified as return data rather than inputs, which usefully prevents the agent from trying to pass them in.

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?

It names a specific resource — the per-industry demo websites plus the shared demo login credentials (company ID, email, password) — which an agent can distinguish from siblings like ubm_about or ubm_list_business_types. The verb is implicit (it 'provides'/'returns' these), so it falls just short of the 5 pattern of explicit verb+resource.

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 phrase 'so the person can click around UBM themselves' implies the usage context (someone wants to explore the product hands-on), but there is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools. The agent must infer that this is the demo/exploration path rather than the signup path.

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