health_query

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

With no annotations provided, the description carries the full burden. It discloses the read-only nature via 'Supports SELECT queries only', which is a significant behavioral trait. However, it does not mention output format variations (beyond schema), potential performance/limits, or error behavior, 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?

The description is a single sentence, immediately stating the action and the key restriction. It is concise and front-loaded, with no wasted words.

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 tool with two parameters and no output schema, the description is adequate: it specifies the action, the data domain, and the central limitation. The output format defaults are in the schema, and the lack of an output schema means return details are not strictly necessary. It is not overly complex, and the description covers the essential context.

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 coverage is 100% with descriptions for both query and format, so the bar is lowered. The description adds the Apple Health data context and the SELECT-only restriction, but these are already partially inferred from the schema. It does not provide deeper semantic 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 executes SQL queries on Apple Health data, with a specific verb ('Execute') and resource. The additional 'Supports SELECT queries only' clarifies scope and distinguishes it from health_report (pre-built reports) and health_schema (schema introspection).

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 provides the constraint that only SELECT queries are allowed, which implicitly says not to use it for writes, but it does not explicitly mention alternatives like health_report or health_schema, nor does it describe when to prefer this tool over siblings. It gives a minor usage hint but lacks explicit when-to-use guidance.

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