get_wellness

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

The annotation readOnlyHint=true already covers the safety profile. The description adds contextual scope (single-day retrieval) but does not disclose any additional behavioral traits such as error handling, rate limits, or authentication requirements. It is consistent with annotations, but the value beyond them is limited.

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 well-structured with a lead sentence, a usage note, and a compact argument list. The Args section is somewhat redundant with the schema, but overall it is concise and scannable.

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 a detailed output schema present and annotations covering read-only behavior, the description sufficiently covers purpose, usage context, and parameter intent. It could mention what specific metrics are returned, but the output schema addresses that. No significant 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 description coverage is 100%, so both parameters are fully described in the schema. The description's Args section simply restates the schema without adding new semantic meaning. This meets the baseline but no more.

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 begins with 'Fetch wellness record for a specific date,' using a specific verb, resource, and scope. It clearly distinguishes from the sibling tool list_wellness, which handles multiple days, by explicitly mentioning the single-day focus.

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?

It provides explicit when-to-use guidance ('when examining a single day's physiological metrics') and explicitly names the alternative for multi-day queries ('To list metrics across multiple days, use list_wellness'). This fully orients the agent.

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