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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful behavioral context beyond annotations: the required XDISPATCH user type and a cost of 1 API credit with the vendor. It does not describe error cases or response shape in depth, but the added auth and billing details are valuable.

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 front-loaded sentence followed by a short endpoint reference. Every element is useful: returned fields, user context, auth requirement, cost, and HTTP path. No filler or repetition.

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 a one-parameter read tool with rich annotations and no output schema, the description is complete enough to invoke correctly. It covers the required user type, cost, endpoint, and the main fields returned, which compensates for the absent output schema.

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 100%, so the single parameter is already documented as 'CXT on-demand order id.' The description reinforces that this is an on-demand order through the endpoint path, but adds no new format, range, or constraint details beyond the schema. The baseline of 3 applies when the schema carries 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 states a specific verb and resource ('One on-demand order with itemized charges') and scopes it to an 'OPERATIONS APP (X Dispatch) user.' This distinguishes it from the sibling cxt_get_order by user perspective and lists the returned content, so an agent can identify its role without opening the schema.

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?

It gives clear context for when to use this tool: when the caller needs the order as an Operations App user and can sign in with user type XDISPATCH. However, it does not explicitly name cxt_get_order as the alternative or state when not to use this tool.

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