roamzy_list_esims

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

Discloses that the tool returns status, balance, and msisdn, and clarifies that id is internal. However, without annotations, it lacks details on pagination, error handling, or read-only nature, leaving some behavioral gaps.

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 sentences cover purpose and critical usage guidance with no redundancy. Every word adds value.

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 no output schema or annotations, the description adequately covers what is returned and important usage rules. Could mention error scenarios or output format, but sufficient for a simple list tool.

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?

Input schema has zero parameters and 100% schema coverage. Baseline for 0 params is 4; no additional parameter info needed as there are none.

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 the authenticated user's eSIMs with specific fields (status, balance, msisdn), using the verb 'list' and specifying the resource. It distinguishes from sibling tools implicitly as others handle countries, orders, etc.

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?

Provides essential guidance on how to refer to eSIMs in user-visible text (use msisdn, not id), which is a clear usage instruction. Does not explicitly address when to use vs. alternatives, but sibling contexts make differentiation straightforward.

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