List Samsung Health Records

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds context of operating on local CSV/ZIP data, which is valuable but not rich in behavioral traits like caching details or error handling.

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?

Description is two brief sentences, no fluff, but could benefit from more structure (e.g., bullet points) for readability. Still efficient.

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 7 parameters and no output schema, the description is too short. Lacks details on return values, caching semantics, and what 'bounded records' means. Incomplete for a tool of this complexity.

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 57%, and description only mentions 'type/start/end filters' without elaborating on purpose, format, or constraints for parameters like privacy_mode, response_format, or incremental_cache. Does not compensate for uncovered schema properties.

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?

Description clearly states it lists bounded records from local Samsung Health export data, with filtering options. Distinguishes from siblings like 'samsung_health_list_workouts' and 'samsung_health_daily_summary' by specifying local export data and bounded records.

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?

Advises using type/start/end filters to keep output small, but does not explicitly compare to sibling tools or state when not to use this tool. Implies usage for filtered record listing, but lacks exclusions or alternatives.

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