Wellness Onboarding Flow

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces 'Read-only.' It adds significant behavioral detail by listing the exact return content (flow, profile, missing fields, hint), going well beyond what annotations provide.

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: the first describes the output, the second gives a clear usage scenario. Every word 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?

Given no output schema, the description covers return fields adequately. With only two optional parameters and no nested objects, the tool is simple. Missing potential details like error handling or limits, but sufficient for a retrieval tool.

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% as only 'locale' has a description; 'response_format' lacks description. The tool description only mentions locales indirectly, providing no additional meaning for 'response_format' or the default behavior.

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 Delx wellness onboarding flow in en or pt-BR, along with current shared profile, missing critical fields, and cross-connector hint, which distinguishes it from sibling tools focused on other Fitbit data.

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 to use when a user starts a fresh wellness session and needs to fill out specific fields, providing clear context. Does not explicitly list exclusion criteria or alternatives, but the narrow purpose makes it effective.

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