get_block_count

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

With no annotations provided, the description carries the full burden. It successfully adds behavioral context by disclosing performance characteristics (lightweight, fast). While it omits explicit readOnly classification, 'Get' implies safe read access appropriate for this data retrieval pattern.

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?

Extremely concise at five words plus parenthetical qualifier. Every element earns its place: the core function ('Get current block height') and the key differentiator ('lightweight, fast'). No redundancy or wasted space.

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 zero-parameter tool with an output schema present, the description is complete. It explains what the tool retrieves and its performance profile without needing to document return values (covered by output schema) or parameters (none exist).

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?

Input schema contains zero parameters. Per scoring rules, zero-parameter tools baseline at 4. The description appropriately focuses on behavior and purpose rather than inventing non-existent parameter documentation.

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?

States specific verb (Get) and resource (current block height). The parenthetical '(lightweight, fast)' effectively distinguishes this from siblings like get_blockchain_info or analyze_block, positioning it as a minimal, fast alternative to heavier data-retrieval tools.

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?

Provides implicit usage guidance through 'lightweight, fast', suggesting use when performance matters and only the height is needed versus detailed analysis. However, it does not explicitly name alternatives (e.g., get_blockchain_info) or state exclusion criteria.

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