cluster_monitor_io

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is reduced. It adds the useful scope detail that results are session-level and include top-waiting statements, but says nothing about freshness, time window, pagination, or result shape for a monitoring feed.

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 compact sentence with no filler. It is slightly awkward ('IO over the session') and buries the tool's actual payload behind a prepositional phrase, but it is appropriately sized.

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 no-argument read-only monitoring tool with no output schema, the description gives a rough sketch of the returned content, which is close to sufficient. It still leaves the agent guessing how this differs from the sibling cluster_monitor_* feeds and what the data covers in time or scope.

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 there is nothing for the description to disambiguate; the baseline of 4 applies.

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 the resource (blob cache IO) and what it returns (session IO plus the statements that waited most on the blob cache), which is more than a restatement of the name. However, it is a noun phrase with no clear verb and does not distinguish itself from close siblings such as cluster_monitor_disk, cluster_monitor_bottomless, or cluster_monitor_remote_stats.

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 only usage signal is the trailing 'for the IO tab', which hints at UI context but never states when an agent should call this versus the other cluster_monitor_* tools. There are no exclusions or alternatives named.

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