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

Annotations already flag readOnlyHint=false and openWorldHint=true, so the write nature is covered. The description adds real behavioral context beyond that: validation against the on-chain market (open status, spec hash) and the submitted artifact, plus the exact return payload. It still omits auth requirements, error behavior, and what state the claim intent creates.

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-loads the action and consumer in the first clause, with the accepted artifact forms compressed into one run-on list and the return value in a short final sentence. Dense but nearly every clause carries information; only 'any deliverable, no forge account' feels extraneous.

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 7-parameter, non-idempotent, open-world mutation with no output schema, the definition covers the artifact input space and return shape but not authentication, failure modes, or the semantics of the four remaining parameters. Adequate to attempt a call, insufficient to call it confidently.

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 0% across 7 parameters, so the description carries the full burden. It clarifies the two required params indirectly — marketId via 'funded market'/'on-chain market' and forgeRef via the artifact URL/CID list — and hints at specHash, but leaves actor, claimant, commits, and forgeUserId undocumented in both schema and description.

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 ('Claim intent on a funded market') and describes the validation path and return value (shipClaim args + attestation token). It implies a distinct role relative to wide_ship_prepare/wide_ship_submit but never names those siblings, so differentiation must be inferred.

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?

The description enumerates acceptable artifact forms (github PR/issue URL, btfs://cid, ipfs://cid, rcpt:// + evidence.receipt, /api/jobs/ record), which tells an agent what inputs qualify. It does not say when to call this versus wide_ship_prepare or wide_ship_submit, nor any prerequisites or when-not-to-use condition.

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