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

The readOnlyHint annotation already declares a safe read, but the description adds real value on top: it runs 'without any signature' (no auth/signing required) and returns execution status, fee, per-entity balance changes and engine logs. It does not mention rate limits or size constraints, keeping it below a 5.

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?

Two tight sentences, front-loaded with the core action and benefit, with the pre-signing workflow guidance placed last. No filler or redundancy.

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?

With no output schema, the description carries the burden of describing returns and does so by naming execution status, fee, balance changes and engine logs. Combined with 100% schema coverage for inputs, an agent has what it needs, though a note on dry-run semantics vs. actual execution would round it out.

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 100%, so every parameter including blobs, network and locale is already documented in the schema; the baseline is 3. The description adds no syntax or format details beyond that (e.g. nothing on blob/manifest relationship), so it does not earn higher.

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 ('Dry-runs a transaction manifest on the Gateway') plus the notable constraint ('without any signature'), and even enumerates what it returns. However, it does not differentiate itself from the close sibling validate_transaction_manifest or explain_manifest, so an agent must still infer which one to pick.

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?

Gives clear workflow context: 'Always preview a manifest before asking the user to sign it,' which tells the agent exactly when in the flow to call this. It offers no explicit exclusions or named alternatives (e.g. when to prefer validate_transaction_manifest), so it stops 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.