report_fulfillment_issue

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

With only openWorldHint present, the description carries the behavioral burden. It usefully discloses that it creates a tracked issue and computes the provider report window (30 days from delivery), which is real value beyond the annotations. However, it omits permissions/auth requirements, whether the issue is editable or reversible after creation, and any idempotency behavior for a mutation 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?

Two front-loaded sentences that earn their place, with the core action stated first and the follow-up chain second. The stray '[#dc88bc]' artifact at the end is meaningless noise that slightly detracts from otherwise tight structure.

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?

No output schema exists, and the description compensates by saying a tracked issue is created and a report window is computed, plus naming the tools that consume the result. For a mutation tool with rich schema coverage, this is nearly complete; only the response shape and permission prerequisites are left implicit.

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 schema already documents all eight parameters including enums and defaults. The description adds little parameter-level meaning beyond restating categories already present in the schema, so the baseline 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?

States a specific verb and resource ('Report a post-sale fulfillment issue (defect) on an order') and enumerates the concrete conditions it covers (mockup mismatch, print quality, damaged, wrong/missing, late/lost). It distinguishes itself from siblings by naming check_fulfillment_issue and resolve_fulfillment_issue as the downstream steps, so an agent can place it in the workflow without opening a 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?

Explicitly routes the agent: report here first, then check_fulfillment_issue for the provider-ready report, and resolve_fulfillment_issue to file/close or create a replacement. It gives clear usage context and sequencing but stops short of stating when NOT to use this tool (e.g. pre-fulfillment or non-fulfillment order problems).

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