GetOrderListLight

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'paginated list' but fails to explain pagination mechanics (e.g., default page size, how to iterate). It also says 'without details' but does not define what details are excluded. For a tool with no annotations, more transparency is needed.

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 deprecation tag. It is extremely concise and front-loads the most important information (deprecation) first. Every word serves a purpose with no redundancy.

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 and no annotations, the description provides the basic purpose. However, for a tool with no parameters, it lacks explanation of what 'all Orders' means (scope, filter), and the pagination aspect is vague. Completeness is adequate but not thorough.

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 and 100% description coverage. For a parameterless tool, the baseline is 4. The description does not add parameter-specific meaning because there are none, but it does mention 'paginated list', which might imply missing parameters for pagination; however, the schema confirms no parameters, so no significant ambiguity.

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 starts with '[DEPRECATED]' to signal status, then clearly states 'Get a paginated list of all Orders without details'. It uses a specific verb ('Get') and resource ('Orders'), and distinguishes itself from sibling tools like GetOrderListFull (which includes details) and GetOrderListLightV3 (the non-deprecated version).

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 deprecates the tool, implying it should not be used. However, it does not suggest an alternative tool like GetOrderListLightV3 or explain when to use this one over others. The phrase 'without details' gives some context but no direct comparison to similar tools.

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