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

With no annotations, the description carries the full burden, and it does disclose the substantive observable states (Day 1–7/14 phases, staging URL, repository transfer, payment) which partially substitutes for the absent output schema. However it omits auth prerequisites (the accessToken requirement is only visible in the schema), error behavior for unknown/expired orders, and any rate-limit guidance for what is clearly a polling tool.

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 sentence with the verb and the four returned signals front-loaded and zero filler. Every clause adds discriminative information an agent can act on.

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 usefully enumerates the returned fields and the phase window, which is most of what an agent needs to decide to call it. The remaining gap is operational detail around polling and auth, which the schema partly covers via the accessToken parameter.

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 100%, so orderId and accessToken are already fully documented in the input schema, including the tf_ord_ prefix hint and the Bearer-header alternative. The description adds nothing parameter-specific beyond the phrase "for an order"; baseline 3 is appropriate.

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?

"Checks current fulfillment phase ... staging URL, repository transfer status, and payment state for an order" gives a specific verb plus a concrete enumeration of what is inspected, which is clearly distinct from the write-oriented siblings (submit_project_spec, negotiate_terms). It stops short of naming a sibling to route against, so it lands at 4 rather than 5.

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?

Usage is only implied: the mention of "current" fulfillment phase and the order-scoped framing suggest post-submission polling, but there is no explicit when-to-use statement, no cadence guidance for a phase-based tracker, and no exclusion telling the agent when another tool is the better call.

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