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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the scope is workspace-wide and enumerates what is reported, which is useful context, but it discloses no additional behavioral traits such as freshness or latency of the figures.

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 that front-loads the primary metric (media volume) and appends the secondary ones. It is a sentence fragment rather than a full sentence, but every clause maps to an actual reported value, so there is no filler.

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, the description must convey what comes back, and it lists the three result categories, which is adequate for a parameterless report tool. It stops short of describing the shape or granularity of the breakdown (e.g. counts vs bytes, what counts as 'recent'), leaving minor ambiguity.

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 of 4 applies; the description cannot add parameter meaning because none exist. The schema is empty and the description correctly does not invent arguments.

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 and the three specific data points reported: chat media volume by type, the media retention window, and recent downloads. An agent can tell this is a read-only reporting tool, though it does not explicitly distinguish itself from nearby storage siblings such as neuron_storage_job or neuron_clear_media.

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 prerequisites, and no mention of alternatives. The only signal is that it is a summary, which implies a read query, but nothing tells the agent when this is preferable to other storage or analytics tools.

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