get_metrics

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

With no annotations, the description carries full responsibility for disclosing behavior. It hints at a real-time read operation, but does not state whether the tool is read-only, what side effects it might have, how data is scoped, or what 'metrics' refers to.

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 only two words long and is under-specified rather than efficiently complete. It contains no verb, no object, and no supplementary detail, so it does not earn credit for conciseness.

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?

A zero-parameter tool still needs context about what it returns and how it differs from at least the most similar siblings. There is no output schema and no clarification of what counts as 'metrics,' making the description inadequate for reliable tool selection.

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 nothing for the description to clarify. The empty input schema covers all parameter semantics by construction, earning the baseline score of 4.

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 'Real-time Metrics' is a noun phrase rather than a statement of what the tool does. It restates the tool name ('metrics') with the modifier 'real-time,' but never specifies a verb or resource, and it does nothing to distinguish get_metrics from sibling tools like get_system_status or get_platform_status.

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 guidance on when to use get_metrics versus any of the many sibling getter tools. The phrase 'Real-time' weakly implies current data, but no context, exclusions, or alternative conditions are provided.

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