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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by specifying the exact behavioral scope: it returns core transaction fields, token transfers, cross-chain leg details, and internal calls, context beyond the structured annotations.

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, tightly written sentence with zero filler. It front-loads the primary purpose ('Full detail for a Wanchain transaction') and then lists the specific content included, making every word informative.

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 simple one-parameter, read-only tool, the description adequately covers what the agent can expect the tool to return by enumerating the detail categories. It does not describe error behavior or response format, but without an output schema and given the tool's simplicity, this is a minor gap rather than a completeness failure.

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%, and the description does not elaborate on the hash parameter at all. The parameter name 'hash' plus the title makes its purpose inferable, but the description does not compensate for the missing schema documentation, nor does it clarify format or domain (transaction hash, not block hash or other identifier).

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 states a specific verb and resource: 'Full detail for a Wanchain transaction' and enumerates the concrete data categories it returns (core fields, token transfers, cross-chain leg, internal calls). This clearly distinguishes it from sibling tools like get_address_activity or get_bridge_activity, which target different resources or scopes.

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?

The intended use is implied by the name and description: call this when you need transaction-level detail. However, it provides no explicit guidance on when to prefer this over potentially related siblings such as get_bridge_activity or get_crosschain_stats, especially given the cross-chain leg mention.

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