Oura Sessions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds only the scope requirement, but does not disclose other behavioral traits such as pagination behavior, rate limits, or response format nuances beyond schema. With annotations covering safety, a score of 3 is appropriate.

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?

The description is a single concise sentence that front-loads the core function. No unnecessary words or 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 the tool has 8 parameters, an output schema (though unseen), and annotations covering safety, the description is largely complete. It states the scope requirement and the types of sessions. However, it lacks elaboration on what constitutes a 'session' or the distinction between guided and unguided, which could be clarified.

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 description coverage is 88%, and parameters have clear descriptions (e.g., after/before converted to Oura dates, pagination controls, privacy_mode, response_format). The description adds no extra meaning beyond the schema; baseline 3 is justified.

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 the tool lists both guided and unguided Oura app sessions, and specifies the condition 'when the user granted session scope'. It uses specific verb and resource, and distinguishes from sibling list tools by focusing on sessions.

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?

The description implies usage when session scope is granted, which is a prerequisite. However, it does not provide explicit guidance on when to use this tool versus alternatives like oura_list_sleep or oura_list_workouts, leaving the agent to infer from context.

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