Show dialplan

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the purpose (call-path tracing) but says nothing about output volume or shape, which matters for a "dump" operation that can return a large dialplan; no pagination or truncation behavior is disclosed.

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?

Two short sentences, zero filler, with the primary scoping behavior front-loaded and the use case trailing as supporting context.

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?

For a read-only, two-parameter inspection tool with full schema coverage and no output schema, the description covers what the agent needs to select and call it. A brief note on expected output size for large contexts would close the remaining gap.

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 100%, with both `context` and `extension` documented including an example context value. The description only restates that extension narrows the output, so it adds no semantics beyond the schema; baseline 3 applies.

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?

States a specific verb (dump) and resource (dialplan) and immediately clarifies the two scoping modes: whole context or a single extension within a context. That precision is enough to distinguish it from every sibling, which all target entirely different resources (channels, endpoints, registrations, status).

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?

Gives a concrete use case — tracing where a call would go before placing it — which tells the agent when this tool is the right choice. It stops short of naming alternatives or stating exclusions, so it is clear context without full routing guidance.

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