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

The description indicates a non-destructive read-only check ('Check if...'), but the annotations state readOnlyHint=false and destructiveHint=true, directly contradicting the description. This is a serious inconsistency that could mislead an agent about side effects. No additional behavioral context (e.g., return format, error cases) is provided.

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 that directly states the purpose without superfluous words. It is concise and well-structured for quick parsing.

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?

While the tool is simple and the description conveys the core purpose, the absence of an output schema means the description should explicitly mention the return value (e.g., boolean) or error behavior. The annotation contradiction further undermines completeness, as it would make an agent uncertain about side effects. Overall, it is minimally adequate but lacks important contextual details.

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?

The schema covers 100% of parameter descriptions, including 'Transaction hash / txid (64-char hex string)', so the description adds no extra semantic value beyond what is already in the schema. The baseline of 3 is appropriate because the schema handles the parameter documentation.

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 action ('Check'), the target resource ('a specific transaction'), and the specific scope ('still in the pending pool (mempool)'). This distinguishes it from siblings like get_transaction or get_pending_transactions, which have different purposes.

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 description implies usage (when you have a transaction ID and want to check pending status) but provides no explicit when-to-use vs alternatives, exclusions, or prerequisites. It does not mention sibling tools like get_transaction for confirmed status, so guidance is limited to implied context.

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