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

Annotations already declare destructiveHint=true and openWorldHint=true, so the irreversible on-chain broadcast profile is partly conveyed structurally. The description adds real value by disclosing per-platform encoding formats and required transaction ordering (create then lock, 0xSplits then coin create), but says nothing about idempotency, failure/partial-submission behavior, or confirmation semantics.

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 dense sentences with no filler; the provenance constraint is front-loaded before the platform-specific encoding and ordering details.

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?

There is no output schema, yet the description never indicates what a successful submission returns (signatures, tx hashes, per-item status) or how partial failures surface. For a destructive, open-world tool with 0% schema description coverage, the flow and format guidance is solid but the response contract 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 description coverage is 0%, so the description must compensate and largely does: it explains that 'signed' originates from crew_build_unsigned and that entries are platform-encoded (base64 vs 0x hex), and that 'platform' must match the builder used. It only implies rather than states the significance of array ordering and the 1-8 item bound.

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 (submit signed transactions) and anchors it to the sibling that produces its input, crew_build_unsigned. An agent can distinguish this from crew_build_unsigned and crew_launch 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?

Clearly positions the tool as the second half of a two-step flow originating in crew_build_unsigned, and adds the operative condition 'Pass platform to match the builder.' It stops short of stating when not to use it or what happens on mismatch/failure.

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