explorer_get_block_by_timestamp

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and variability. The description adds that it returns a block number, which is useful, but it does not disclose potential edge cases, precision details, or behavior when timestamps fall outside chain range. Meets the baseline with annotations but no extra depth.

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 succinct sentence that front-loads the core purpose and includes the key 'before or after' qualifier. Every word earns its place, with no redundancy or filler.

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 three-parameter lookup tool with no output schema, the description gives the essential purpose and return type (block number). However, it does not specify the exact return format or handle edge cases like timestamp outside chain history. It is minimally adequate but not comprehensive.

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 descriptions cover 100% of parameters, and the description adds minimal value by restating the 'before or after' behavior and the output is a block number. It does not provide syntax examples or clarify edge cases beyond schema. Baseline 3 is appropriate given full schema coverage.

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 finds the block number closest to a given Unix timestamp, with the 'before or after' option. This is a specific verb-resource combination and distinguishes it from siblings like explorer_get_block which likely fetches by block number or hash.

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 when to use it (when you need a block near a timestamp), but it does not explicitly mention alternatives or exclusion scenarios. It lacks the explicit 'use X instead' guidance seen in higher-scoring examples. The usage context is clear but not elaborated.

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