CGM onboarding

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

No annotations provided, but description discloses 'Read-only', 'non-secret data only', and storage location (~/.delx-wellness/profile.json), compensating for lack of annotations with important behavioral context.

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 zero waste; every sentence adds value. Front-loaded with purpose and key constraints.

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 one optional parameter and no output schema, description fully covers what the tool returns, its purpose, and security considerations. No gaps.

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%; description adds no extra meaning to the locale parameter beyond what schema already provides ('Defaults to en'). Baseline 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?

Description clearly states 'Returns the 11-question onboarding flow for the shared Delx Wellness profile. Read-only.' This is a specific verb (returns) and resource (onboarding flow), distinguishing it from siblings like cgm_profile_get.

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' providing clear context for when to use. Does not include when-not-to-use or alternatives, but context is strong.

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