icu_update_sport_settings

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

Annotations indicate a non-readonly, non-destructive, idempotent write operation. The description adds value by clarifying the partial update semantics ('Only fields you pass are sent'), which goes beyond what annotations provide. No contradictions detected.

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?

Two concise sentences front-load the purpose and partial update behavior. Every word adds value with no redundancy.

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?

Given the simple structure (5 params, 1 required, output schema present), the description is complete. It explains the core operation and update strategy without needing to detail return values.

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?

Input schema covers all 5 parameters with individual descriptions. The description adds the critical behavioral note that the tool performs a partial update, meaning omitted fields are left unchanged. This enriches the schema information.

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?

Description uses specific verb 'Update' and identifies the resource as 'per-sport threshold record', listing the fields involved (FTP/FTHR/pace/swim). This clearly distinguishes it from sibling tools like icu_create_sport_settings.

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 usage for updating existing records but provides no explicit guidance on when to use this tool vs. alternatives like icu_create_sport_settings or icu_apply_sport_settings. The partial update behavior is stated but not contrasted with other update patterns.

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