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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that this is a GET on a summary endpoint returning static attributes, which mildly disambiguates it from live/time-series data, but says nothing about auth scope, error behavior, single-profile vs multi-provider resolution, or rate limits.

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 the purpose front-loaded and the API route as a compact cross-reference. Nothing is padded or repeated.

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 two-parameter read-only tool with full schema coverage and no output schema, the description is nearly sufficient: it names what the resource is and hints at returned attributes. It stops short of clarifying the provider filter's effect or how this differs from other user-oriented 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 100%, so both parameters (user_id, provider) are already documented, including the provider slug examples. The description only echoes the user_id path segment and adds no filtering semantics, so the baseline 3 applies.

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 gives a specific verb and resource ('Get a user's profile summary') and lists sample returned fields ('height, and other static attributes'), so the agent knows what comes back. It does not, however, differentiate itself from siblings like vital_get_user or vital_get_user_latest_info, which sound closely related.

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 guidance on when to prefer this over vital_get_user, vital_get_user_latest_info, or vital_get_body. Usage is only implied by the name and by the 'static attributes' phrasing, leaving the agent to guess at routing.

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