Oura Agent Manifest

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

Annotations already mark readOnly, idempotent, non-destructive. Description adds the critical fact that it does not call Oura or expose secrets, which is valuable beyond 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?

Single sentence packs purpose and a key behavioral constraint with zero wasted words. Front-loads essential info.

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 the tool's simplicity (2 optional enum params, output schema exists), the description provides enough for basic use. Could mention that output is a manifest with install/runtime guidance, but annotations and context signals fill 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?

Two parameters with enums but 0% schema coverage. Description says nothing about 'client' or 'response_format' — their meanings, defaults, or how they affect the output. Agents must guess their purpose.

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 the tool provides machine-readable guidance for AI agents, not actual Oura data. This distinguishes it from siblings like oura_get_personal_info which make API calls.

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 'Does not call Oura or expose secrets,' guiding agents to use this when they need manifest info rather than data. Could be improved by noting when to use alternatives, but context signals with many data-retrieval siblings make it clear.

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