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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no indication of whether it performs an on-chain lookup, requires a live node, or how long a proof check takes. The 'BRP-100' token implies a standard spec but it is never explained.

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?

It is short, but brevity here is under-specification rather than conciseness: a bracketed tag and a jargon code occupy the whole description and convey no actionable front-loaded information.

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?

This is a five-required-parameter tool with zero documented parameters and no output schema, so the description carries the entire explanatory burden — and it provides none. An agent cannot construct a valid, meaningful call from this definition alone.

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?

All five required parameters (bridge_id, source_chain, dest_chain, amount, token) have 0% schema description coverage and the description supplies no meaning for any of them. Format expectations — chain identifiers vs names, token symbol vs address, amount units/decimals — are entirely undocumented.

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 is essentially a restatement of the title plus an opaque standard code: '[defi] Bridge Proof (BRP-100-BridgeIntegrity)'. It hints at a proof/verification domain but never states a verb or what is being verified (a transfer, a message, a lock event), so an agent cannot tell it apart from defi_oracle_verify, verify_settlement, or forge_verify beyond the 'defi bridge' label.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative among the many verify-style siblings. The agent must guess whether this validates a pending bridge transaction, a proof payload, or post-hoc integrity.

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