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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the useful detail that token transfers are included in the returned details, but it does not disclose any additional behavioral traits such as missing transaction handling or chain-scoping effects.

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 description is a single, front-loaded sentence with no filler. It earns its place but is slightly too sparse to fully compensate for missing usage and parameter context.

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?

An output schema exists, so return-value details are less necessary, but the description still lacks when-to-use guidance and parameter semantics. For a tool with dozens of siblings and an undocumented chain parameter, this is not complete enough for reliable selection and invocation.

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 0%, so the description should compensate, but it does not explain what transaction_hash or chain mean or how they affect results. 'transaction_hash' is somewhat self-explanatory, and 'chain' has a default of 'all', but the description gives no parameter-level guidance.

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 uses a clear verb ('Get') and names the resource ('transaction details') with a specific scope ('comprehensive ... including token transfers'). It is distinguishable from address- and token-focused siblings, but it does not explicitly mention lookup by transaction hash, which leaves slight ambiguity versus address_transactions.

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 guidance is given about when to use this tool instead of alternatives such as address_transactions, token_transfers, or prediction_market_lookup. There is no stated context, prerequisite, or exclusion, so an agent must infer when this is the right choice.

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