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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the trailing 'Read-only.' largely restates structured data. The description does add that the order-scoped call also returns 'report-window eligibility,' a useful behavioral detail, but says nothing about result volume, pagination behavior beyond schema fields, or what an 'issue' contains.

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?

Front-loaded with the core action and mode split in three tight sentences; almost no waste. The unexplained trailing tag '[#533758]' is unexplained noise and the only reason this is not a 5.

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 6-parameter read tool with no output schema, the description does enough: it defines both call shapes and the filter scoping rule. It could say more about the shape of a returned issue or pagination semantics, but nothing essential to calling it correctly is missing.

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 baseline is 3, but the description adds a genuine cross-parameter rule the schema does not state: the inbox filters (status, store, limit/offset) apply only when order_uuid is absent. It also restates the 'open_any' expansion, which the enum description already covers.

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 verb+resource ('List fulfillment issues') and goes further by delineating two distinct modes (per-order vs. workspace-wide inbox), which cleanly separates it from siblings like check_fulfillment_issue, report_fulfillment_issue, and resolve_fulfillment_issue.

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?

Explains when to use each mode ('With order_uuid... Without: the workspace-wide issues inbox') and what filtering is available, giving clear invocation context. It stops short of naming an explicit alternative or exclusion condition, so it is not a full 5.

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