Delx Wellness Onboarding Flow

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description reinforces 'Read-only — does NOT persist anything' and adds context about returning 11 questions, profile state, missing fields, and 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?

Three sentences with no wasted words. First sentence states core purpose, second reinforces safety, third gives pairing guidance and cross-connector note. Front-loaded and efficient.

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 and no output schema, the description adequately covers what is returned (onboarding flow, profile state, missing fields) and how to use it (pair with update). Minor omission: no description of response format differences, but overall sufficient.

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 50% (locale described, response_format missing). The tool description adds no parameter information, failing to compensate for the gap. The response_format enum values 'markdown' and 'json' are not explained, leaving ambiguity.

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 the tool returns the 11-question onboarding flow plus current profile state and missing fields. It specifies the verb 'return' and resource, and distinguishes from siblings like apple_health_profile_get by including the onboarding flow.

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 advises pairing with apple_health_profile_update after user answers, providing clear usage context. Lacks explicit when-not-to-use guidance, but the pairing instruction sufficiently differentiates from alternative tools.

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