getFixedTermOrder

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

Annotations already declare read-only behavior, and the description adds valuable operational details: cursor-based pagination, a required parameter dependency, a default filtering behavior, and a rate limit. It does not cover ordering or time-boundary semantics, but it goes well beyond the annotations.

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 compact and well-organized: a one-line purpose, two focused notes, and a rate limit. Every sentence adds functional value without unnecessary detail.

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?

For an 8-parameter read-only query with no output schema, the description gives the essential dependencies and pagination behavior, making it usable. However, it does not explain the meaning of time-range parameters, cursor mechanics, or what fields the returned order history contains.

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%, so the description carries the burden of explaining parameters. It clarifies productId/category coupling, orderType default, and cursor-based pagination, but leaves startTime, endTime, orderId, and cursor mechanics mostly to inference from names and types.

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 identifies a specific operation and resource: 'Query fixed term order history.' This distinguishes it from related siblings like getFixedTermPosition or placeFixedTermOrder, and the pagination note further defines its 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?

The description provides clear context for when to use this tool—fetching fixed term order history—and adds important behavioral guidance such as the productId/category dependency and default orderType behavior. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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