agentlens_stats

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

No annotations are provided, so the description carries the full burden. It describes the two actions and their outputs (storage stats, overview metrics) and includes an example. However, it does not disclose whether the tool has side effects, requires authentication, or has rate limits. Given the read-only nature implied by 'get', a 3 is appropriate.

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 concise with no wasted words. It uses a clear structure: one-line summary, when-to-use sentence, bulleted actions with descriptions, and a code example. Every sentence serves a purpose.

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 that the tool has only one parameter with 100% schema coverage and no output schema, the description does enough. It explains both action values and gives an example. While it could be more precise about the exact fields in the output (e.g., specific metrics returned), it is not required since there is no output schema to complement.

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?

Schema coverage is 100% with a single parameter 'action' defined as an enum. The description adds meaning by explaining the enum values ('storage': Get storage stats, 'overview': Get overview metrics) beyond the schema's 'Action to perform'. This helps the agent understand the parameter's semantics clearly.

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 the tool retrieves storage statistics and system overview metrics. It distinguishes itself from sibling tools by specifying 'storage statistics' and 'system overview' which are not covered by other agentlens_* tools like agentlens_agents or agentlens_alerts. However, it could be more precise about the exact scope of metrics.

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?

Provides explicit when-to-use guidance: 'To check database/storage utilization or get a high-level system overview.' It also lists the two actions with descriptions, which helps an agent decide which action to invoke. Does not explicitly state when not to use or list alternatives, but the sibling tools cover other domains, so the context is clear.

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