resolve_fulfillment_issue

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

With only openWorldHint in annotations, the description carries the burden and does well: it discloses that submit_upstream records the upstream filing and returns a dashboard link plus summary, that resolve closes the issue, and that create_replacement builds a zero-charge draft order. It also names failure modes and says the error tells you what to do instead. Permissions, idempotency, and reversibility are still unstated.

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?

Three front-loaded sentences that walk through actions in lifecycle order with no filler; each sentence earns its place. A stray '[#a819f9]' token at the end is noise.

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 multi-action mutation tool with no output schema and minimal annotations, the description covers action semantics, required pairings, and create_replacement failure modes. Return values are only described for submit_upstream, leaving the other two actions' responses 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 coverage is 100%, so the baseline is 3, but the description adds real context by mapping parameters to actions (claim reference is 'optionally' used with submit_upstream, resolution_type is required for resolve) and by spelling out the six resolution_type values with their intent.

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?

Names a specific verb and resource ('progress a fulfillment issue') and then enumerates the three lifecycle actions with distinct effects, so an agent can tell it apart from report_fulfillment_issue, check_fulfillment_issue, and list_fulfillment_issues 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?

Each action is tied to a concrete situation ('records that the problem report was filed', 'closes it with a resolution_type', 'builds a one-click zero-charge replacement'), which gives clear context for choosing among them. It does not state prerequisites (e.g., that an issue must already exist via report_fulfillment_issue) or when not to use the tool.

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