customers_orders

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

The description discloses a behavioral trait: the tool requires a higher plan to access. However, with no annotations and no description of the operation, return format, or side effects, this single detail carries little weight. The tool's core behavior remains hidden.

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 a single sentence with a clear upgrade tag, directly pointing to a relevant action. It is front-loaded and contains no fluff, making it extremely concise and well-structured.

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?

The description is severely incomplete. It does not state what the tool does, what it returns, or any operational context. With no annotations, no output schema, and no parameter details, this one-line gate message is insufficient for an agent to understand or safely invoke the 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?

The tool has zero parameters, so the schema provides no parameter details. According to the rubric, a baseline of 4 applies for zero-parameter tools since the description does not need to compensate for missing parameter semantics.

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 only states that an upgrade is required and directs to license_status, but it never explains what the customers_orders tool actually does. The tool name hints at customer orders, but the description provides no verb or resource to clarify its function.

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?

There is no guidance on when to use this tool versus sibling tools like orders_list or customers_list. The mention of license_status is about upgrade options, not about choosing between tools.

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