reset_buffer_metrics

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

With no annotations, the description carries the full behavioral burden and does disclose two real prerequisites (write permission and the `metrics` feature flag) plus the scope (all records, running instance). It does not explicitly warn that the current counter values are irreversibly lost or state the response, but for a reset tool the prerequisites and scope are meaningful disclosures beyond the schema.

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 front-loaded sentence with the action and scope first and the prerequisites tucked into a parenthetical. Zero wasted words.

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?

No output schema or annotations exist, so the description must stand alone; it covers purpose, scope, and prerequisites adequately for a reset operation. It leaves minor gaps around the result of the reset and confirmation of irreversibility, but nothing essential to calling it correctly is missing.

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 description coverage is 100% and the single endpoint parameter is fully documented in the schema (formats, AIMDB_CONNECT fallback). The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (reset) and resource (buffer introspection counters produced/consumed/dropped/occupancy) with the scope 'for every record on a running AimDB instance'. This is clearly distinct from the read-side sibling get_buffer_metrics and from reset_stage_profiling, but the description never names the alternatives, so it relies on the resource noun to differentiate.

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?

Usage is implied: you reset the counters when you want to clear them (e.g. before a fresh measurement window). The description gives the enabling conditions (write permission, metrics feature) but offers no explicit when-to-use vs when-not, and never references the read counterpart get_buffer_metrics or reset_stage_profiling.

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