get_transaction_status

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation but says nothing about behavior when a transaction is not found, whether an unconfirmed/pending transaction behaves differently, or what 'status' values are returned — meaningful gaps for a transaction-status tool.

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 front-loaded sentence with no filler; the resource and lookup key come first. 'and details' is slightly vague but does not waste space.

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 two-parameter getter with full schema coverage this is minimally adequate. However, with no output schema and no annotations, the description could profitably say what 'status' and 'details' encompass (e.g., success/failure, finality) to be fully complete.

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 the schema already documents both tx_hash and sender_id, setting the baseline at 3. The description adds no syntax or format detail, and its 'by its hash' phrasing omits the required sender_id, though the schema compensates.

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 ('Get') and resource ('status and details of a NEAR transaction') and scopes it to a lookup by hash, so the agent can distinguish it from siblings like get_block_info or get_account_info. It stops short of explicitly naming an alternative or contrasting purpose.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternative tools. The agent must infer that this is the tool for post-submission transaction lookup from the name alone.

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