list_domains

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds valuable behavioral context: results are paged, filter_name is an exact match, filter_access has specific valid values, include supports theme, and no mutation endpoint exists for domains. This fully discloses observable behavior without contradicting annotations.

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 front-loaded with the core purpose, then provides precise parameter semantics, pagination rules, and a read-only note in compact bullet-like paragraphs. Every sentence adds useful information without redundancy or filler.

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?

The description covers the domain concept, the primary use case, pagination details, filter semantics, read-only constraints, and required OAuth scope. Since an output schema exists, return-value documentation is unnecessary; the description is sufficient for an agent to invoke the tool 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?

With 0% schema description coverage, the description compensates well: filter_name is exact hostname match, filter_access has three explicit values, include supports theme, and page_cursor is tied to pagination. page_size is not explicitly described, but its meaning is clear from the parameter name and the 'one page at a time' framing.

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 description opens with a specific verb and resource: 'List the organization's training domains, one page at a time.' It further clarifies the domain concept and distinguishes this listing tool from related tools like get_domain by noting it returns pages and supplies the domain_id used by publish_courses.

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 explicitly states when to use this tool ('this is where to find the domain_id that publish_courses needs'), explains pagination behavior ('when has_more is true, call again with next_cursor'), and notes that domains are read-only with no create/change tool. It also tells agents which OAuth scope is required.

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