yeastar_list_itsp_trunks

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

No annotations are provided, so the description carries the behavioral burden. It clarifies that this lists a template catalog rather than configured trunks, and the verb 'List' implies a read-only operation. It does not elaborate on return shape or pagination behavior, but for a simple paginated list tool the scope clarification is the most important behavioral trait.

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, well-structured sentence with zero wasted words. The core purpose is front-loaded, and the critical sibling distinction is included in the same sentence without making it unwieldy.

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 simple list tool with two optional pagination parameters and no output schema, the description is complete: it identifies the exact resource, clarifies what it is not, and names the alternative. An agent has everything needed to decide whether to call this tool and with what parameters.

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%, so the schema already fully documents both parameters (page and page_size). The description adds no parameter-specific detail, but none is needed because the schema handles it.

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 states a specific verb ('List') and resource ('ITSP (VoIP provider) templates available on this appliance for trunk creation'), and explicitly distinguishes it from configured trunks. This makes the tool's purpose unambiguous and clearly differentiates it from yeastar_list_trunks.

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 explicitly says when to use this tool (for ITSP templates used in trunk creation) and when not to use it (for the appliance's own configured trunks), and even names the correct sibling tool (yeastar_list_trunks). This gives the agent direct routing guidance.

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