Delx Wellness Onboarding Flow

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description reinforces read-only behavior, adds specifics about the output (11 questions, profile state, missing fields), and mentions cross-connector sharing, adding value beyond annotations.

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: first declares purpose and output, second adds usage guidance and cross-connector context. No wasted words, front-loaded with key information.

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 read-only tool with two optional parameters, the description covers purpose, output content, pairing suggestion, and cross-connector context. Annotations handle safety. No missing critical information.

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 coverage is 50% (one of two parameters described). The description does not add details about parameters beyond the schema; it mentions the onboarding flow but not how locale or response_format affect it. Baseline 3 is appropriate given moderate coverage.

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 clearly states the action: 'Return the 11-question onboarding flow plus the current profile state and missing fields.' It distinguishes from siblings (e.g., profile_get, profile_update) by specifying the onboarding flow and cross-connector sharing.

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?

Explicitly states it is read-only and does not persist, and advises pairing with samsung_health_profile_update for actual updates. Mentions cross-connector sharing to set context for multi-source profiles.

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