block_heights

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

With no annotations, the description carries full behavioral burden. It clarifies required parameters, pagination defaults, and return data (block heights, timestamps). Does not disclose rate limits or authentication, but the read-only nature is implied and no contradictions.

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?

Three sentences: purpose, parameters, and returns. No unnecessary words, front-loaded with the common use case. Every sentence adds value.

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?

Describes return data as 'block heights, timestamps, and related data' which is slightly vague but adequate. Lacks output schema, but the description covers key aspects. Pagination and required parameters are clear.

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 baseline is 3. Description restates schema details (format, defaults) without adding new meaning beyond what is already in 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 states 'get all the block heights within a particular date range', specifying the verb (get), resource (block heights), and scope (date range). It clearly distinguishes from sibling tools like 'block' which retrieves a single block.

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?

Description implies usage for historical analysis and time-based queries but does not explicitly state when not to use or mention alternatives like 'block' or 'transactions_for_block'. Provides some context but lacks direct guidance.

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