system_global_usage_latest

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

There are no annotations, so the description carries the full behavioral burden. It only names the returned data and implies a read operation, but does not state whether this is a live or cached snapshot, whether admin privileges are required, or what side effects, if any, exist.

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?

The description is short and wastes no words, but it is a noun-phrase fragment rather than a complete action statement. It is concise, yet under-specified enough that the structure does not add much beyond the tool name.

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 zero parameters and an output schema present, the basic invocation is clear and return values can be learned from the schema. However, with many similar system_* siblings and no annotations, the description lacks enough context to reliably route an agent to this tool over the closely related resource usage variants.

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 has zero parameters, so there is no parameter documentation burden on the description. The empty input schema fully covers the invocation surface.

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 ('global resource usage') and a temporal scope ('latest'), so an agent can tell this returns a current system-wide usage snapshot. It lacks an explicit verb and does not differentiate from the closely named system_resource_usage_latest, but the core purpose is clear.

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?

No guidance is given about when to use this tool versus system_resource_usage_latest, system_global_usage_history, or other system monitoring siblings. The description provides no selection criteria or exclusions.

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