get_v1_kaspa_derivatives_recent_blocks

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

No annotations are provided so the description carries full burden. It states the tool returns recent blocks with max 144 and optional filter but does not disclose return format auth needs or rate limits. For a read-only endpoint this is minimally adequate but lacks detail.

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 relatively short but includes unnecessary details like price and category. The mention of a nonexistent parameter harms clarity. Structure is acceptable but accuracy is compromised.

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?

Given zero parameters and no output schema the description should fully document the tool. It omits the definition of the mentioned 'chain_only' parameter and does not describe the response format. This leaves the agent without critical information.

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 input schema has zero properties but the description mentions an optional 'chain_only' flag which is not present in the schema. This is misleading and contradictory thus the description fails to add meaningful parameter semantics.

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 returns recent Kaspa blocks with a maximum of 144 per call an optional chain_only filter. It distinguishes itself from sibling tools like get_v1_kaspa_derivatives_blocks_block_hash which fetches specific blocks.

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 indicates it is for backtesters and indexers and includes note about informational research data. However it does not explicitly compare to sibling tools or state when not to use this tool.

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