Oura Onboarding (shared wellness profile)

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

Declares read-only behavior, matches annotations (readOnlyHint, idempotentHint, non-destructive), and adds context about subsequent update step. 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, front-loaded with main purpose, no wasted words. Efficient and structured.

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?

With no output schema, the description clarifies return content (flow + profile state + missing fields) and usage pattern, plus relates to sibling tools. Complete for a read-only onboarding 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 covers 50% of params with descriptions (locale has description, response_format has default and enum but no description). Description adds that locale can be 'en' or 'pt-BR' and that response_format defaults to markdown, plus context about the flow. Adds value beyond schema.

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 it returns the 11-question wellness onboarding flow plus profile state and missing fields, and distinguishes from sibling tools by noting that all connectors share the same profile and questions.

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?

Provides explicit guidance: the agent should ask questions one-by-one, then call oura_profile_update. Also explains when to use this vs other connector onboarding tools.

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