Delx Wellness Onboarding Flow

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

Annotations already declare read-only and non-destructive, and the description reinforces this with 'Read-only — does NOT persist anything.' It also discloses cross-connector profile sharing, which is additional behavioral context beyond the annotations. No contradiction.

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 that are front-loaded and concise: purpose, read-only caveat, pairing instruction, and cross-connector context. Every sentence adds value with no redundancy.

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 covers what is returned, the non-persistence behavior, the pairing with profile_update, and cross-connector sharing. It is complete enough for an agent to invoke correctly.

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 only 50%: locale has a description but response_format lacks any schema or description-level guidance. The description does not mention parameters, failing to compensate for the undocumented response_format semantic.

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 it returns the 11-question onboarding flow plus the current profile state and missing fields, using a specific verb ('Return') and distinct resource. This differentiates it from sibling tools like google_health_profile_get and google_health_profile_update.

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 instructs to pair with google_health_profile_update once the user answers, giving a clear usage sequence and naming the relevant alternative. This provides strong when-to-use guidance relative to siblings.

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