vechainstats_get_block_daily_stats

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists some returned content (gas used, transaction count) but omits details like whether the data is cached, how the 'expanded' parameter changes behavior, or any permissions/rate limits. The read-only nature is implied but not explicitly stated.

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?

A single sentence that is front-loaded with the action and resource. It is appropriately brief for a simple tool, though the trailing 'etc.' is a bit vague. No filler or redundancy.

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?

With no output schema, no annotations, and one undocumented parameter, the description is insufficient for fully understanding behavior and return structure. It gives a high-level summary but leaves key specifics (e.g., exact stats included, expanded effect) to inference, making it incomplete for a tool in a large family.

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 50%: 'date' is documented, but 'expanded' has no description. The tool description does not explain what 'expanded' controls, so parameter semantics are incomplete. The description adds no value beyond the date field already defined 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?

Clear verb+resource: 'Get' + 'daily block statistics', with examples of content (gas used, transaction count). The 'daily' qualifier distinguishes it from sibling tools like get_block_info (specific block) and get_network_stats (network-wide), so the purpose is specific and non-misleading.

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 the use case: when you need daily aggregate block statistics for a given date. However, it does not explicitly state when to use this tool over alternatives like get_block_info or get_network_stats, nor are there any exclusions or alternative references.

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