check_fulfillment_issue

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the redundant 'Read-only' adds nothing, but the description adds real behavioral context: the report is returned by default (include_report defaults true) and the tool only prepares a copy-paste summary_text plus a deep-link because providers require filing in their own dashboards. That tells the agent the tool does not actually file the claim.

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 main action is front-loaded and the content is dense and information-rich, but it is delivered as one sprawling compound sentence with heavy parentheticals. The trailing '[#2f6bdb]' fragment is an unexplained artifact that earns no place and slightly degrades the definition.

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?

With no output schema, the description carries the burden of describing returns and does so well by enumerating the issue contents and the shape of the report (summary_text plus deep-link). It is essentially complete for calling the tool; only explicit routing guidance versus sibling issue tools 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 issue_uuid and workspace semantics are already covered and the baseline is 3. The description adds meaning beyond the schema by explaining what include_report actually produces (a summary_text and a provider dashboard deep-link), which clarifies the consequence of the parameter rather than just restating it.

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 (fetch) and resource (one fulfillment issue), then enumerates exactly what 'in full' contains: affected items, evidence attachments, provider claim tracking, resolution, plus the optional provider-ready report. The singular 'one' plus the 'in full' framing cleanly separates it from the sibling list_fulfillment_issues.

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 implied rather than stated: an agent can infer this is the detail view after list_fulfillment_issues, and the note that Printful/Printify accept problem reports only in their own dashboards explains the report's purpose. But there is no explicit when-to-use or when-to-avoid guidance relative to siblings like list_fulfillment_issues, report_fulfillment_issue, or resolve_fulfillment_issue.

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