bridge_deadlines

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

With no annotations, the description carries the full burden, and it does deliver meaningful behavioral context: it is a paid tool ($0.02 USDC per call via x402 on Base or Solana) and it explicitly states failure behavior (returns 402 payment instructions instead of data). That is strong disclosure. It stops short of describing the return shape or ordering of results.

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?

Three compact fragments, front-loaded with the resource, then payment terms, then the parameter. Every clause earns its place; nothing redundant or padded.

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 one-parameter read tool with no output schema, the description covers purpose and payment mechanics adequately, but does not convey what a returned item looks like or how results are ordered, which matters when there is no output schema to fall back on.

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 100% and the single 'limit' parameter is fully documented in the schema (min 1, max 200, default 50). The description repeats 'Optional limit 1-200' without adding format or behavioral detail, so the baseline 3 applies.

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 resource and scope: 'upcoming class-action and claim deadlines', with a clarifying gloss ('money with an expiry date'). An agent can tell it apart from siblings like bridge_bounties or bridge_opportunities, though it doesn't name those alternatives. Clear verb+resource.

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?

No when-to-use guidance and no named alternatives among the many sibling tools. The 'money with an expiry date' gloss implies the domain but doesn't tell the agent when to prefer this over bridge_opportunities or bridge_bounties. Usage must be inferred.

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