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

Annotations already provide readOnlyHint=true)Skip. The description adds concrete behavioral details: it returns all domain templates, each with key, status (ACTIVE or COMING_SOON), and a provisioning summaryikuha; it also clarifies the purpose of discovering which templates are currently applicable. No contradiction; it doesn't mention pagination/limits, but for a zero-param list tool this is not a meaningful gap.

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?

Three sentences, each earning its place: definition, output summary, and usage guidance. Information is front-loaded with the core function and the key restriction for calling it.

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 covers the essential return fields and the reason to call it. It doesn't explain filtering or pagination, but for a zero-parameter list-all endpoint, those are unlikely and not necessary for correct invocation.

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?

Input schema has zero parameters)Skip. Baseline 4 applies: there are no params to document)Skip. Description adds value by explaining the entries' content, compensating for the absence of an output 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?

Clearly states the tool lists all domain templates and defines what a domain template is, with specific output fields. It distinguishes itself from the sibling preview/apply tools by framing list as the discovery step.

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?

Explicitly instructs when to call it: 'Call this before preview or apply to discover which templates can currently be applied.' This tells the agent the temporal relationship with siblings and helps avoid calling preview/apply for unavailable templates.

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