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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true), so the bar is lower; the description adds genuinely useful behavioral context by disclosing the expected transaction ordering per platform ('create then lock', '0xSplits then coin create'). It stops short of stating failure/irreversibility behavior for a destructive on-chain submission.

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, then platform-specific payload formats in dense telegraphic fragments. No wasted sentences, though the abbreviated syntax is slightly harder to parse than a full sentence would be.

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 destructive, open-world submission tool with no output schema and 0% schema coverage, the definition covers input provenance and ordering but omits what happens on success/failure and whether any platform values lack supported orderings. Adequate but with real gaps.

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 carry parameter meaning; it does explain that 'signed' holds platform-specific payloads (Solana base64 vs EIP-1559 hex) and that 'platform' must match the builder. It still leaves array length bounds, per-item constraints, and the remaining enum values (clanker, vibevibe, sui) unexplained.

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 ('Submit signed transactions') and explicitly ties the input to the sibling that produces it ('from crew_build_unsigned'). An agent can distinguish this submission step from the builder without opening either 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?

Clear context: use this after crew_build_unsigned, and 'Pass platform to match the builder' gives an explicit consistency rule. No explicit when-not or error-path guidance, but the workflow slot is unambiguous.

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