dialplan_list_rules

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

With no annotations, the description carries the full burden for behavioral disclosure. It implies a non-destructive read operation via the verb 'List', but does not explicitly state that it is read-only, any authentication requirements, or side effects. It is minimally adequate.

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?

A single sentence of 10 words, front-loaded with the main action. Every word is necessary, no redundancy. Excellent conciseness.

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 core purpose and the optional filter, but omits mention of pagination (limit/offset) and does not explain the output schema. Given the tool's simplicity and presence of an output schema, it is minimally complete but could be improved with notes on limit/offset defaults.

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?

Schema description coverage is 0%. The description only hints at the 'dpid' parameter ('optionally filtered by dialplan id') but does not explain 'limit' or 'offset'. No additional meaning is added beyond the schema, failing to compensate for the lack of descriptions in the 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?

The description clearly states the verb 'List' and the resource 'dialplan rules', and mentions optional filtering by dialplan id. This exactly identifies the tool's function and distinguishes it from sibling tools like add, delete, or reload.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or compare with similar list tools like drouting_list_rules or dialplan_translate.

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