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

Annotations already cover read-only and open-world behavior, and the description adds genuinely useful error semantics beyond that: `{}` returned on 404 rather than throwing, other errors re-raised, and the validation applied to the UUID. That is meaningful disclosure an agent cannot get from the annotations alone.

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?

Compact and front-loaded: the outcome (usage totals, `{}` when unknown) comes first, followed by the mechanism and error handling. No padding, though the backtick-heavy style is a bit dense to read.

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, the description takes on the job of describing the return value, and it does so (`{}` on unknown/404, otherwise usage totals). The only real gap is the absence of any routing guidance among the many gear-related siblings.

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 0%, so the description carries the parameter burden, and it does: `gearUUID` is validated via `validateUuid` with hex characters and optional hyphens. The exact accepted format is specified, which the bare string-typed schema does not convey.

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 resource and outcome: usage totals for one piece of gear. That clearly separates it from siblings like get_gear (gear records) and get_gear_activities (activities tied to gear), though it never explicitly names an 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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives like get_gear or get_gear_activities. The reader can infer you call it with a known gearUUID, but nothing distinguishes the situations where this tool is the right pick.

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