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

Annotations already establish the safe, read-only, idempotent profile, and the description adds substantial return-behavior detail: it explains the fallback when the latest reset did not cover every user and lists every applicable banked reset. This is meaningful behavioral context beyond what the annotations provide.

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 front-loaded with the core object and its contents, followed by a compact use-case clause. Both sentences earn their place and contain no filler.

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 simple read-only tool with one schema-documented parameter and no output schema, the description supplies the necessary return semantics, fallback behavior, and usage examples. Annotations cover the safety profile, so nothing critical 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 only parameter is a provider enum already well documented in the schema. The description mentions Claude in examples but adds no meaning beyond the schema's enum descriptions, so the baseline of 3 is appropriate.

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 gives a specific verb and resource ('most recent usage-limit reset') and enumerates the returned fields, making the tool's scope clear. It does not explicitly distinguish itself from its siblings get_reset_stats or list_resets, so sibling differentiation is only implicit.

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?

It provides clear usage context through example questions: 'when did Claude last reset usage limits?' and 'do I have a banked reset to use?'. It does not state when not to use this tool or name the alternative sibling tools for other scenarios.

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