Get P-Chain tx status

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the description is not fully burdened. The description adds the detail about returning a reason when dropped, which is useful, but does not disclose rate limits, error handling, or other behavioral nuances. With annotations present, this is adequate but not exceptional.

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?

A single, tightly written sentence that first states the action, then the possible results, then the usage context. No wasted words, and the information is front-loaded with the purpose.

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 read-only tool with well-documented parameters and no output schema, the description covers the core need: what it returns (statuses, including drop reason) and when to use it. It is complete enough for an agent to call correctly, though it could optionally mention that 'Unknown' may mean a recently submitted transaction.

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 both tx_id and network are already documented. The description adds usage context that implies tx_id comes from the mentioned transaction types, but it does not add format or additional parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool checks a P-Chain transaction status with specific possible values (Committed, Processing, Dropped, Unknown) and includes the underlying API (platform.getTxStatus). It distinguishes itself from siblings like avax_get_transaction or avax_get_chain_status by focusing on P-Chain transaction status with explicit status outcomes.

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 explicitly says 'Use after AddSubnetValidator/ConvertSubnetToL1/CreateChain transactions', giving clear context on when to invoke this tool. However, it does not mention when not to use it or point to alternative tools for other chain transactions, so it lacks explicit exclusions or alternatives.

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