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

The description states 'Idempotent (same status twice succeeds quietly)', but the annotations declare idempotentHint=false, a direct contradiction an agent would act on when deciding whether to retry. There is also tension with destructiveHint=false given that cancel can trigger a refund, restock inventory and reset self-reported sales. Rich context aside, the explicit conflict with structured metadata forces a 1 per the contradiction rule.

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 organized as action → permission → edge cases → docs link; nearly every clause carries operational weight. It is dense and slightly run-on, and domain terms like 'rikma' and 'till' are used without definition, which costs a point.

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 5-parameter mutation tool with no output schema and a rich annotation set, the description covers the gaps that matter: permissions per action, permission boundaries, idempotency, invalid transitions, restock defaulting, and a docs URL. An agent has everything needed to call it correctly aside from the annotation conflict noted above.

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, and the description goes beyond it by tying the action enum values to workflow consequences (shipped = parcel left, fulfilled = delivered/picked up, cancel = refund) and by explaining when the restock default flips (only when not yet shipped). It adds little on orderRef/projectId format, which the schema 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+target set: advancing a paid store order to shipped, fulfilled, or cancel. An agent can immediately distinguish it from getRikmaOrderTool/listRikmaOrdersTool (reads) and from setShopStockTool (inventory).

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 by actor and condition: any member may mark shipped/fulfilled, cancel is holder-only because it resets their own self-reported sales, and sales already in a split are left for the rikma to settle. It also states behavioral rules (idempotent repeats, backwards transitions refused, restock default) so the agent knows when the call is legal before invoking it.

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