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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the 'Read-only' sentence is largely redundant. The description does add useful behavioral context by identifying these as orders stuck before the fulfillment provider, but says nothing about pagination, result size, or ordering, which matters for a list 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?

The purpose is front-loaded and the three sentences are short, but the appended token '[#80ba1e]' is stray noise with no meaning, and 'Read-only' duplicates the annotation. The definition is not bloated, but only the middle sentences earn their place.

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 two-parameter read-only list tool with no output schema, the description supplies enough to call it correctly: the resource, its scope, and the reconciliation-view context. It correctly does not need to describe return values, though more on result shape or ordering would have pushed it higher.

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 both parameters (store_uuid, workspace) are already documented, including the agency-scoping semantics of workspace. The description adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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 ('List orders in a store that have pending fulfillment data needing attention') and adds a qualifier ('orders that stalled before reaching the provider') that helps distinguish it from the many order/fulfillment siblings. It is clearer than a generic list tool, though it never names an explicit sibling it should not be confused with.

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?

'Use to find orders that stalled before reaching the provider' gives an implied use case, and mentioning the reconciliation view adds context. However, with near neighbours like list_fulfillment_issues, check_fulfillment_issue and reconcile_order in the toolset, there is no when-not guidance or explicit alternative routing, leaving the agent to infer the boundary.

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