get_performance_metrics

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

With no annotations, the description carries the full burden. It simply says 'Get current performance metrics and statistics' without disclosing side effects, resource usage, or whether it requires a prior setup. No behavioral traits are disclosed beyond the obvious read-only nature of 'get'.

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 very short, consisting of two sentences, and gets to the point immediately. However, 'performance metrics' and 'performance statistics' are slightly redundant, but overall it is appropriately concise.

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?

Given there are zero parameters and an output schema exists, the description sufficiently covers the tool's purpose. It doesn't elaborate on the exact metrics included, but that is presumably handled by the output schema.

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?

This tool takes no parameters, and the schema confirms this with an empty properties object. The baseline score of 4 is appropriate since there is nothing for the description to add.

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 clearly states 'Get current performance metrics and statistics', indicating a read-only retrieval operation. This contrasts with sibling tools like reset_performance_metrics, making the purpose unambiguous.

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 information is provided about when to use this tool versus alternatives. There is no mention of when it's appropriate to call this, or that reset_performance_metrics is for clearing metrics.

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