List Tegro.money orders

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

No annotations provided, so description must carry full burden. It omits behavioral traits such as pagination, sorting, response format, or rate limits, leaving agents uninformed.

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?

Though short, the description is under-informative. It fails to include critical details that would justify its brevity, such as output or pagination behavior.

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?

With no annotations, no output schema, and minimal parameter info, the description is incomplete. It does not describe return values, pagination, error handling, or authentication nuances beyond the API key.

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 coverage is 0% and description does not mention the 'page' parameter. No explanation of its purpose, default, or behavior, so adds no value over 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 'List the shop's orders' clearly states the action (list) and resource (orders), distinguishing it from sibling tools like tegro_get_order (single order) and tegro_list_shops (shops).

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?

Only mentions the prerequisite 'Needs TEGRO_API_KEY' but provides no guidance on when to use this tool vs alternatives like tegro_get_order or tegro_create_order.

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