linode_list_domains

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

Annotations already declare readOnlyHint=true, so the descriptive behavior is consistent. The description adds context about the returned fields (type, status, SOA email), which is valuable beyond the schema. No contradictions.

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 a single sentence with an additional use-case hint. Every word contributes value, and it is front-loaded with the core action. No unnecessary information.

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 primary functionality and fits within the expected complexity of a simple list tool. However, the missing parameter semantics and lack of pagination or filtering details reduce completeness, especially since the schema provides enums but no explanation.

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 description fails to explain the 'detail' parameter, which controls the level of detail (concise vs full). With 0% schema description coverage, the description should compensate but does not, leaving the agent unaware of how to control output verbosity.

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 clearly states the verb 'List', the resource 'DNS domains (zones)', and includes additional details like type, status, and SOA email. It distinguishes from sibling tools like 'linode_get_domain' by implying a listing action.

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 says 'Use to inventory DNS zones', providing a clear use case. However, it does not explicitly mention when not to use this tool or suggest alternatives, such as using 'linode_get_domain' for a single domain.

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