pmg_domains_list

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

No annotations are provided, so the description bears full burden. It states the tool is read-only ('read') and requires a config. It does not disclose additional behavioral traits such as pagination, response size limits, or whether it lists all domains unconditionally. The verification note adds reliability context but not behavioral detail.

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 concise, with a clear first-line summary and a brief verification note. Every sentence adds value, though the verification line could be considered extraneous for an AI agent. Overall efficient and well-structured.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the core purpose and prerequisites. However, for a list tool among many siblings, it could be more specific about scope (e.g., 'all domains' vs. filtered). Adequate but not fully comprehensive.

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 sole parameter 'proximo_target' is fully defined in the input schema with a clear description. The tool description adds no additional parameter semantics. With 100% schema coverage, baseline score of 3 is appropriate.

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 'List PMG managed mail domains (read)', providing a specific verb (list) and resource (PMG managed mail domains). It distinguishes from siblings like pmg_domain_create and pmg_domain_delete, which are for create/delete operations.

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 notes 'Needs PROXIMO_PMG_* config', specifying a prerequisite. It implies read-only use but does not explicitly contrast with other list tools or provide when-not-to-use guidance. The context of siblings makes the domain listing usage clear.

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