Cycle onboarding

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

Discloses read-only and non-secret data stored at a specific path. With no annotations, description carries full burden. It adds value but doesn't detail return format or behavior on repeated calls.

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, front-loaded with purpose, then usage guidance. No unnecessary words.

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?

Adequately describes purpose and usage but lacks details on the return value (e.g., array of questions). Given no output schema, some additional context would be beneficial.

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 100% with one parameter 'locale' already described. The description adds no extra info about parameters. Baseline score of 3 is appropriate.

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?

Clearly states the tool returns the 11-question onboarding flow for the shared Delx Wellness profile. It is read-only and specifies the purpose: to personalize responses for the wellness stack. This distinguishes it from sibling tools like cycle_quickstart or cycle_demo.

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 says 'The agent should ask these questions next' which guides when to use. It ties to personalization for wellness-cycle-coach and other tools. No explicit when-not-to-use, but context is clear.

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