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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool is non-custodial, validates with testmempoolaccept before relaying, never relays rejected transactions, and is disabled by default unless RB_ENABLE_BROADCAST=1 is set. This is substantial, useful behavioral context for a mutating action.

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?

The description is compact and every sentence earns its place: purpose, validation behavior, deployment flag, and usage context are all covered without repetition or fluff. It is front-loaded with the core action before supporting 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?

For a two-parameter tool with no output schema and no annotations, the description covers the key operational concerns: what the tool does, how it validates, when it should be used, and its deployment availability. The main missing piece is what the tool returns (e.g., txid or error), which would be useful given there is no output schema.

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 50%: signed_raw_tx_hex has a terse description and chain is just an enum. The description confirms the transaction is already-signed but does not add meaningful parameter-level detail beyond the schema, such as hex format expectations or what chain values mean. It is adequate but not compensating.

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?

The description states a specific action ('Relay an already-signed raw transaction to the network') and clearly identifies the resource and delivery mechanism ('through our own full node'). It also distinguishes this tool from the read-only sibling tools by emphasizing that it is a broadcast/write action, so an agent can immediately tell what it does.

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 gives an explicit use case: 'an agent signed locally and wants a high-availability broadcast path.' This provides clear context for when to use the tool, though it does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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