get_sleep_log

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

The description implies a read-only operation ('Get') and specifies what is returned, which is helpful. Given that no annotations are provided, it does not disclose behaviors such as date formatting expectations, null date handling, or any potential errors, leaving some gaps.

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?

Two concise sentences deliver the essential purpose and return fields without any unnecessary words. Every word earns its place.

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 one-parameter tool with an output schema, the description covers the core purpose and return fields. It lacks details about date formatting and null behavior, but the output schema likely handles return structure. Overall adequate but not exhaustive.

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?

The schema shows a single 'date' parameter with type string/null and a default of null, but no description. The tool description mentions 'for a date' which aligns with the parameter but does not specify the expected format or semantics of null, so it adds minimal meaning beyond the 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?

The description clearly states the tool retrieves sleep data for a specific date and lists the returned metrics (duration, stages, efficiency). The resource is unambiguous and distinct from sibling tools like heart rate or weight logs.

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 phrase 'for a date' provides clear context for when to use this tool—when sleep data for a specific date is needed. However, it does not explicitly mention alternatives or exclusions, which would elevate it to a 5.

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