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

The readOnlyHint annotation already declares this is a safe read. The description adds the underlying REST route (GET /v2/user/providers/{user_id}), which is modest extra context, but says nothing about permissions, empty-result behavior, or what a connected provider entry contains.

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 short sentences with zero waste; the substantive statement comes first and the endpoint mapping is a compact second clause. Nothing is redundant or padded.

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?

A single-parameter read tool whose safety profile is covered by annotations, so completeness requirements are light. It is nearly sufficient, though it never hints at the shape of the returned provider list, which would help with a tool that has no output schema.

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%, so user_id (a Vital UUID) is already documented in the schema. The description only echoes it as a path segment, adding no format or constraint detail. Baseline 3 applies when the schema fully carries parameter documentation.

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 verb (List) and resource (wearables/data sources a user has connected), and the user-scoping implicitly separates it from the sibling vital_list_providers, which is a global provider catalog. An agent can pick correctly between the two without opening either schema.

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?

Usage is implied by the description ('providers a user has connected'), but there is no explicit when-to-use, when-not-to-use, or named alternative. The contrast with vital_list_providers is left for the agent to infer rather than stated.

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