getAdvanceEarnOrder

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

With no annotations, the description must disclose behavior. It states the tool is a query (safe read) and includes permission/rate limit info, but omits details on pagination, response structure, or what 'order history' entails (e.g., only advance earn orders).

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 concise sentences front-load purpose and add essential constraints (permission, rate limit). However, the brevity sacrifices necessary detail for a tool with many parameters.

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, no annotations, 8 parameters with 0% schema coverage, and many sibling tools, the description is critically incomplete. It fails to explain tool behavior, parameter meanings, or return value, making it hard for an agent to use correctly.

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 0%, and the description does not explain any of the 8 parameters (category, productId, orderId, etc.). This forces the agent to infer meaning from names alone, which is insufficient for correct invocation.

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 queries order history, but does not distinguish it from sibling tools like getOrderHistory or getEarnOrderHistory. The name includes 'AdvanceEarn' which implies specialization, but the description does not leverage this to clarify scope.

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?

No guidance on when to use this tool vs alternatives. The description mentions required Earn permission and rate limit, but does not specify contexts (e.g., filtering by category or pagination).

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