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

The readOnlyHint annotation already establishes this is a safe read, and the description is consistent with that. It adds the useful context that the data is static/attribute-based rather than time-series, but it does not describe response shape, authentication, or failure behavior beyond the annotation.

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 sentences with no filler; the core purpose is front-loaded and the API path is useful. Every clause earns its place.

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 two-parameter read endpoint, this is nearly complete: purpose, a sample attribute, and the exact GET endpoint are present, while the schema covers both parameters. With no output schema, it could optionally say more about the returned shape, but the summary term and 'static attributes' convey the expected content well enough.

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 and provider are already documented in the input schema. The description only adds the endpoint path containing user_id; it does not add new meaning to either parameter.

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 states a specific action ('Get') and resource ('user's profile summary') with an example attribute ('height') and the exact API path. It does not explicitly compare against sibling tools like vital_get_user, but 'static attributes' implicitly separates it from the time-series and lab-test getters.

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?

No guidance is given about when to choose this tool over siblings such as vital_get_user or vital_get_body, and no exclusions or prerequisites are mentioned. The only implied use is 'when you need the profile summary,' which is not enough for tool selection among many similar get_* endpoints.

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