create_gear

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

This is the description's strength: it discloses defaults (`usageType="DISTANCE"`, `notes=""`), transformations (date formatting, upper-casing via `validateSportKey`), and exact unit-conversion formulas with floors for the two max-usage fields. It also states the response is returned unchecked, which warns the agent that no validation occurs.

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?

Information-dense and free of filler, but delivered as a single semicolon-chained run-on rather than being front-loaded or structured. The most decision-relevant content (the unit conversions) is buried mid-sentence.

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 10-parameter write tool with no output schema, the description thoroughly covers behavioral quirks but incompletely covers the parameter set, leaving half the inputs unexplained. Annotations supply the safety profile, but an agent still lacks guidance on several required/optional fields.

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?

With only 10% schema description coverage, the description carries heavy load and does add real meaning for the tricky params: the two `maxUsage*Km/Min` conversions, the `usageType` default, `firstUseDate` routing, and `gearType` upper-casing. But `name`, `brand`, `model`, `notes`, and `activityTypeKeys` are left entirely undocumented in both schema and description.

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 pairs a specific verb/resource (POST to `/gear-service/gear/v2` for gear creation) with concrete behavioral detail, so an agent can identify it as the gear-creation tool. It does not, however, distinguish itself from siblings like `add_gear_to_activity`, `get_gear`, or `delete_gear`, and never states the purpose in plain language.

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 explicit when-to-use or when-not-to-use guidance. The only cross-tool reference is a behavioral contrast with `addWeighIn`'s unit-handling rule, which is a note on consistency, not a routing signal to help pick between create_gear and its siblings.

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