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

Beyond the readOnly/openWorld/destructive annotations, it explains provenance (decoded from task board events), exact inclusion rules (successful outbound and paid transactions), ordering (newest first), pagination (cursor), and units (base-unit integer strings). This is substantial behavioral context.

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?

Front-loaded and dense with no filler, but the first sentence is a long chain of clauses that could be broken up for easier scanning. Still appropriately sized for the amount of return detail provided.

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?

There is no output schema, so the description carries the return-value burden; it does that well with inclusion rules, ordering, pagination, and units. It is slightly incomplete on optional parameter semantics (limit) and error/empty behavior.

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?

With 0% schema description coverage, the description adds meaning for address (Wanchain address) and cursor (cursor pagination), but says nothing about limit and does not clarify cursor format or address encoding. It partially compensates for the schema gap.

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?

Names a specific resource (Bridge to Earn activity) scoped to a Wanchain address and states the data source (task board events). This is clearly distinguishable from list_bridge_to_earn_tasks and get_bridge_activity by its address-level, event-decoded activity focus, even without naming siblings.

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?

It gives clear context that this is for an address's Bridge to Earn activity, so use is implied. It does not say when to prefer it over list_bridge_to_earn_tasks, get_bridge_activity, or prepare_bridge_to_earn, nor note prerequisites or exclusions.

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