Sync a Bopster market

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

With no annotations, the description does real work: it discloses that the call changes nothing on-chain, moves no funds, and that the chain remains the source of truth. It also explains the observable effect (site and other tools update immediately). It stops short of stating failure behavior when tx_hash is unconfirmed or invalid, or whether the call is idempotent.

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 sentences, front-loaded with the action and the reason, then the safety clarification. Every clause carries information; nothing is redundant.

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 three-parameter, no-output, unannotated tool, the description covers purpose, trigger timing and side-effect safety. It omits what the tool returns or does on failure, which is a modest gap since 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 description coverage is 100%, so market, wallet and tx_hash are already documented with types and patterns; baseline 3 applies. The description reinforces that tx_hash is a confirmed transaction and that the tool acts on that market, but adds no format or edge-case semantics beyond the schema.

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 gives a specific verb and resource ('Ask the Bopster backend to re-read a market from the chain') plus the exact triggering condition ('after a transaction confirms'). It is clearly a refresh trigger rather than a read, which separates it from get_market/list_markets in spirit, but it never names those siblings, so a 4 rather than a 5.

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 states the precise moment to call it: after a transaction confirms, instead of waiting for the next indexer pass. That is clear usage context, but there are no explicit exclusions (e.g. do not call before confirmation, do not call if the tx reverted) and no sibling tool is named as an alternative.

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