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

No annotations are provided, so the description carries the full disclosure burden and delivers almost none: it does not say whether the lookup is read-only for unaffiliated orders, what statuses exist, how unknown/expired ids are handled, or whether any auth is needed. The presence of an output schema excuses it from describing return values, but the behavioral gaps remain substantial.

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?

A single short sentence with no filler, and the identifying detail (SideShift) is front-loaded. It is terse to the point of under-specification, but nothing is wasted.

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?

Output schema exists, so return values need not be explained, and the tool is a single-parameter lookup. However, given zero annotation coverage and zero schema description coverage, the description should at least state where the id originates and that the call is a read; it does not.

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 coverage is 0% and the single 'id' parameter is undocumented in both schema and description. With no annotations to lean on, the description should clarify that 'id' is the order identifier returned by the order-creation tool, but it only hints at this with "created here".

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?

States a specific resource (a SideShift order) and operation (fetching its status), and the provider name distinguishes it from cow_order_status and debridge_order_status siblings. The verb is nominalized ("Status of...") and "created here" leaves the originating tool implicit, but the intent is decipherable.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative is offered. "created here" weakly implies the id comes from another tool on this server, but the agent must infer that crosschain_create_shift is the producer.

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