get_recent_pending_transactions

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

With no annotations, the description carries the full burden but only says 'from monitoring' – it doesn't explain whether this queries a live monitor, requires an active monitoring session, or what 'recent' means (time window). No behavioral details about freshness, ordering, or prerequisites are given.

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 short sentence, which is concise, but it is under-specified rather than efficiently informative. 'from monitoring' is vague filler that doesn't earn its place.

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 tool with 2 parameters (one undocumented), no annotations, no output schema, and a confusing parameter description mismatch, the description is completely inadequate. It doesn't explain what 'recent' means, the monitoring dependency, or how to use the filters.

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 50%: 'limit' has no description, and 'minValueETH' says 'Filter by minimum CHZ value' which is confusing since the parameter name references ETH but the description says CHZ. The tool description adds no parameter meaning at all, leaving the 'limit' parameter and the ETH/CHZ discrepancy unexplained.

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+resource ('Get recent pending transactions') but adds the vague qualifier 'from monitoring' which doesn't clarify scope or distinguish it from sibling tools like 'get_recent_logs' or 'get_recent_blocks'. It's understandable but lacks the sibling differentiation found in higher-scoring definitions.

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 guidance on when to use this tool versus alternatives such as 'start_pending_tx_monitoring' or other transaction retrieval tools. No exclusions, prerequisites, or context are provided.

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