roamzy_support

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It details exactly what the tool returns (Telegram bot, email, recovery procedure, required info, response times, refund policy) and why it's preferred over alternatives, giving complete transparency about its behavior.

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 front-loaded with a crucial warning, then efficiently lists all use cases and output details. Every sentence serves a purpose without redundancy, achieving high informational density in a compact form.

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 zero parameters and no output schema, the description must explain the tool's function and return value comprehensively. It succeeds by detailing contact methods, recovery procedure, required user info, response times, and refund policy, leaving no gaps.

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 input schema has zero parameters, so schema coverage is 100%. The description adds no parameter information, which is appropriate since there are none. Baseline for 0 params is 4, and the description does not need to add anything beyond 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 that this tool is for contacting Roamzy tech support, filing refunds, and recovering eSIMs, with specific actions and resources mentioned. It distinguishes itself from web searching by warning about lookalike companies, making the purpose precise and unambiguous.

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 tells the agent to call this tool instead of web-searching and lists exact scenarios (support contact, refund, recovery). It also warns against misrouting to lookalike companies, providing clear when-to-use and when-not-to-use guidance.

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