stats

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

No annotations are present, and the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, return format, read-only nature, or any operational characteristics.

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 extremely brief, which might seem concise, but it is under-specified. 'Memory statistics.' is a vague fragment that does not earn its place without additional meaningful content.

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 or annotations, the description needs to explain what statistics are returned and in what form. It fails to do so, leaving the tool's behavior almost entirely ambiguous.

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 the baseline score is 4. The empty schema and the description imply there are no inputs to explain.

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 'Memory statistics.' is a noun phrase that essentially restates the tool name with a domain qualifier. It provides no action verb and does not differentiate from sibling tools such as memory_status or similarity_report.

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 this tool versus alternatives. No context, prerequisites, or exclusions are provided.

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