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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the lower bar applies. The description adds the aggregation scope ('across the validator set'), which is genuinely useful, but says nothing about the return shape, whether the data is windowed, or how large the response may be. Note the readOnly/idempotentHint=false pairing in the annotations is internally odd, but the description does not contradict it.

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 front-loaded sentence with the verb first and no filler, caveats, or redundant restatement of the name. Nothing could be removed without losing content.

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 parameters and no output schema, the description only needs to convey what comes back, and it does so at a high level. However, for a metrics endpoint it leaves open whether results are per-validator rows or a single aggregate, and whether there is a default time window, which an agent would want to know before calling.

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 (empty schema, additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 names a specific resource (TSS keygen and keysign timing metrics) and a clear scope (across the validator set), using the verb 'Returns'. It is distinguishable in spirit from the per-validator siblings get_keygen, get_keysign, and get_keygen_metric, but it never names them explicitly, so the differentiation is left to inference.

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?

There is no when-to-use guidance, no conditions, and no mention of the closely related siblings (get_keygen, get_keygen_metric, get_keysign). An agent must guess whether this aggregate view or the per-key tools is the right choice. The absence of any routing language is a clear gap.

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