koios_blocks

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

With no annotations provided, the description carries the full burden. It discloses ordering (latest first) and pagination support, but lacks information about default limits, response shape, whether it returns full block details or summaries, rate limits, or any other side effects. Minimal behavioral disclosure beyond the obvious read operation.

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?

Single, focused sentence that leads with the main verb and resource, followed by core details. No fluff or repetition of schema information. Highly concise and well-structured.

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 list endpoint with fully documented schema parameters, the description covers the core functionality. However, with no output schema, it doesn't mention return value structure or defaults (e.g., block id vs full block). It is adequate but leaves some gaps for a complete understanding.

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 all parameters are already documented. The description adds 'latest first' and 'pagination support' which aligns with the order and limit/offset parameters, but doesn't explain parameter interactions or provide syntax examples. It meets the baseline but doesn't enhance meaning beyond the schema.

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?

Description has a clear verb (Get), resource (blocks), and distinguishing details (latest first, pagination support). It contrasts with sibling tools like block_info or block_txs, which handle specific blocks or transactions, making the purpose unambiguous.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that for a single block you'd use koios_block_info, or that this is the primary list endpoint. The description only states what it does, not when to choose it.

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