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

Annotations already declare readOnlyHint=true, so the closing "Read-only" is partly redundant; however the description adds genuine behavioural context beyond the annotation, disclosing that the returned state includes live agent state and that the settings explain why a demo lane refused. It stops short of describing auth/permission needs or freshness of the returned settings.

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 purpose is front-loaded in the first clause and the follow-on sentences carry routing and diagnostic value. The single-sentence enumeration of return fields is dense and would read better as a short list, but each element is load-bearing given there is no output schema.

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 output schema, the description carries the full burden of describing return values and does so thoroughly, naming each field group (TTLs, TTL caps, domain overrides, dns_root_domain vs dns_root_domain_default). For a zero-parameter read tool it is complete enough to answer the questions an agent would call it for.

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?

The tool takes zero parameters, so the baseline is 4 and the description appropriately spends its words on output semantics rather than inventing parameter guidance. No parameter-level meaning is needed or missing.

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 the organisation's AI environment settings") and then enumerates the concrete contents: staging cluster for ephemeral AI workspaces and PR demos, workspace/demo TTLs, per-role TTL caps, demo preview domain overrides, and dns_root_domain. An agent can distinguish this from neighbours like get_ai_settings, get_application_demo_config, and get_preview_domain without opening any schema.

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 when-to-use conditions ("Call this before deploying a PR demo or workspace to check the staging cluster is configured and online, and to answer why a demo lane refused") and names the complementary sibling get_preview_domain with the distinction between them. Nothing about selection is left to inference.

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