stalwart_list_dkim_signatures

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'List' implies a read-only operation, and the mention of 'selector + stage' gives a hint about the return content. However, it does not explicitly confirm that the operation is non-destructive or describe any permissions, rate limits, or other side effects, leaving some ambiguity.

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 extremely concise, consisting of two sentences: the first clearly states the tool's purpose, and the second explains the parameter. No unnecessary information is included, making it easy to parse quickly.

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 the low complexity of a list tool and the existence of an output schema (which is assumed to describe the return format), the description is reasonably complete. It specifies the entity (DKIM signing keys), the output fields (selector and stage), and the optional filter. It does not mention pagination or sorting, but these are likely covered by the output schema or are not critical for a basic list operation.

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 domain_id is explained in the description as an optional filter and the source for valid values is given (from stalwart_list_domains). Since the schema provides only a generic title with no description (0% coverage), this explanation fully compensates and adds meaningful guidance.

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 tool lists DKIM signing keys with selector and stage, using the specific verb 'List' and a concrete resource. This distinguishes it from sibling list tools like stalwart_list_accounts and stalwart_list_domains by naming the DKIM-specific entity.

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 provides context for the optional domain_id filter and tells the agent where to obtain valid domain IDs (from stalwart_list_domains). This is a useful guideline, though it does not explicitly state when to use this tool over alternatives like stalwart_generate_dkim or when not to use it.

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