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

Beyond the readOnly/openWorld annotations, it defines what 'confirmed' means (3+ networks in the window), warns the label is a lead not a verdict, points at confirmed_block_layer.window_end, and discloses that under-review layers withhold counts and leave review.verdict unknown. That is substantive interpretation and failure-mode context an agent could not infer from structured fields.

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?

Front-loaded with the use case, then caveats; every sentence carries semantic weight. Slight deduction for dense, run-on phrasing ('Country and domain pairs Voidly labels confirmed means...') that costs some readability.

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 input params and no output schema, the description carries the burden and does so: what is counted, which layer's window is relevant, how to read 'confirmed', and what happens under review. An agent can call and interpret results without further information.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly describes it as a parameterless global summary and spends its words on interpretation instead.

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 a specific resource and scope: counts of countries, networks and domains measured plus the window dates of the confirmed-block layer. 'Global overview' contrasts clearly with the per-country sibling voidly_country_data, though no sibling is named explicitly.

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?

'Use this for a global overview...' sets a clear context for invocation, and 'Domains outside the measured set have no finding' bounds what the tool can answer. It stops short of naming alternatives (voidly_country_data, voidly_incident_stats) for drill-down needs.

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