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

Annotations already declare the tool as read-only, idempotent, and non-destructive, covering the safety profile. The description adds the fact that OAuth binding is done once in the app, which is useful context. However, it does not disclose other behaviors such as rate limits, error handling, or typical response characteristics beyond saying the path follows the provider's docs. With annotations present, this is adequate but not rich.

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 concise—two sentences—yet packed with essential information: the tool's purpose, the provider options, and example paths. It is front-loaded with the core purpose and immediately provides actionable examples. There is no filler or 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?

For a simple proxy with only two parameters and no output schema, the description covers the input semantics well but leaves the return format implicit ('the path follows the provider's docs'). It does not describe error cases, pagination, or how the response relates to the provider's API. Given the tool's simplicity, it is adequate but could benefit from a note that the response mirrors the provider's API format.

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?

The schema provides only parameter names and an enum for provider, with zero description coverage. The tool description compensates by explaining the 'path' parameter with concrete examples for each provider (e.g., Whoop 'v1/cycle', Strava 'api/v3/athlete'), which adds significant meaning. The 'provider' parameter is self-explanatory via its enum. Although not exhaustive, it provides enough semantic context for correct usage.

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 clearly states it is an HTTP bridge to the official APIs of wearables (Whoop, Strava, Oura) linked to the account. It provides specific example paths, which clarifies its role as a proxy. While it doesn't use a standard verb like 'get' or 'fetch', the intent is clear and distinct from the more specialized sibling tools like dietaai_libre_data or dietaai_sibionics_data.

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 implicitly suggests usage when needing data from these wearable providers, but it does not provide explicit guidance on when to choose this tool over the specialized siblings. It mentions that OAuth is already bound, which is a prerequisite, but lacks direct 'use when' or 'prefer if' statements. The context is understandable but not explicitly framed as a decision guide.

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