stat_db_list_load

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

Annotations already declare this a safe read-only, closed-world operation, so the bar is lower. The description adds the important scoping facts of 'average' and 'over a month', which go beyond the annotations, but says nothing about pagination, result ordering, or rate behavior for a statistics endpoint.

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?

A single short sentence that is front-loaded and wastes no words. It is appropriately sized for a zero-parameter stats tool, though the language mismatch with all sibling tools slightly hurts immediate parsing.

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?

For a zero-parameter tool with an output schema present and full annotation coverage, the description need not explain return values. It communicates scope and aggregation sufficiently; naming the per-database sibling would complete it.

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?

There are zero parameters, so the baseline is 4. The description correctly implies the fixed scope (all databases, one month) so the agent understands no arguments are needed and why.

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 ('Average load across all databases over a month') states a specific metric and scope, distinguishing it from siblings like stat_db_load (likely per-database). However, it is written in Russian while the tool name and every sibling are English/Latin, and it does not explicitly name stat_db_load as the per-database alternative.

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?

The description implies a monthly, per-database-list aggregation but gives no explicit when-to-use or when-not-to-use guidance. It neither points to stat_db_load for a single database nor states any preconditions, leaving the agent to infer selection from the name alone.

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