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

Annotations already declare readOnly/idempotent/non-destructive, so 'Read-only' is largely redundant. However, the description adds real behavioral context beyond the structured fields: what the response interprets (launch registration state, trade fill, ETH paid on claims) and the ~1 minute lag of market data. It does not discuss failure modes like unknown or dropped hashes, which keeps it from a 5.

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, both loaded with useful content, and the outcome taxonomy comes first while the usage guidance follows. The CoinFactory enumeration is long but each clause adds a distinct case an agent may need to act on; only minor trimming is possible.

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 must carry the return-value burden, and it does so by describing all the result categories (status, gas, launch/trade/approval/claim interpretation). For a single-parameter read tool this is complete enough to call correctly.

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?

Only one parameter (txHash) and schema description coverage is 100%, so the schema fully documents it. The description adds no format, chain, or validation detail beyond what the schema already says ('0x… transaction hash on Base'), so the baseline of 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 verb+resource ('get_transaction_status' expanded as pending/mined/reverted status, gas cost) and then enumerates the CoinFactory-specific interpretations it returns (launch + registration, trade fill, approval, reward claim with ETH paid). It is clearly distinguishable from the build_* siblings, which construct transactions rather than read their outcome.

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?

Explicitly tells the agent when to use it ('after sending each step from the build tools') and names the alternative to avoid ('instead of guessing from market data, which lags by about a minute'), with the reason. The routing decision is unambiguous.

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