Eight Sleep Data Inventory

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

The description adds a key behavioral fact beyond the readOnlyHint and idempotentHint annotations: the tool does not call any Eight Sleep APIs. This is valuable because read-only could still imply external calls; the description removes that ambiguity. It also advertises that the tool offers recommendations, which is useful context for the agent.

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 short sentences with no fluff. The primary purpose is front-loaded, and the crucial no-API-call qualifier follows immediately. 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 inventory tool with one optional parameter, a full output schema, and annotations declaring it read-only, idempotent, and non-destructive, the description covers everything needed: what it inventories, that it provides recommended first calls, and that it has no external side effects. Nothing material is missing.

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 description coverage is 0%, and the description does not mention the response_format parameter at all. Although the enum values (markdown/json) and default are self-explanatory, the description provides no guidance about which format to choose or how the parameter affects output, so it fails to compensate for the low schema coverage.

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 uses a specific verb ('Inventory') and names the resource: supported Eight Sleep domains, mutation tools, and recommended first calls. It also explicitly distinguishes itself from API-calling siblings by stating 'Does not call Eight Sleep APIs,' making its role as a metadata/inventory tool unmistakable.

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 clearly implies use when an agent needs an overview of supported domains, mutation tools, or recommended starting points. The explicit exclusion 'Does not call Eight Sleep APIs' tells the agent this is not for data retrieval or mutation, though it does not name specific sibling alternatives or provide explicit when-to-use/when-not-to-use language.

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