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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether this is a read-only verification or a mutating action, what authorizations or credentials are required, whether it is idempotent, or what happens on failure.

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 text is short, but its brevity comes from under-specification rather than conciseness. An opaque internal code is not a substitute for a front-loaded statement of what the tool does.

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 no annotations, no output schema, and no parameter documentation, so the description must supply everything and supplies nothing. An agent cannot safely construct a call from this definition.

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 parameters (bridge_id, source_chain, dest_chain, amount, token) have 0% schema description coverage, and the description adds no meaning for any of them. Formats, accepted chain identifiers, token notation, and units for amount are all 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 reduces to a domain tag ('[defi]') plus a label ('Bridge Proof') and an internal protocol code ('BRP-100-BridgeIntegrity'). It never states a verb or the actual operation being performed, and gives no basis for distinguishing it from siblings like defi_oracle_verify, defi_contract_audit, or rng_verify.

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 guidance whatsoever on when to call this tool, what preconditions must hold, or which sibling to prefer for adjacent tasks. The codename 'BRP-100-BridgeIntegrity' offers no actionable selection criteria.

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