Samsung Health Export Freshness

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

Adds behavioral details beyond annotations: it returns mtime, days_since_export, is_stale flag based on defined conditions. Annotations already indicate readOnly and idempotent, so description complements well.

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 efficient, front-loading purpose and return values. Could be slightly more concise, but no wasted sentences.

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?

Describes return values adequately for a read-only tool, but omits explanation of the response_format parameter. Without output schema, the description covers main aspects but misses the parameter detail.

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 only parameter (response_format) is not mentioned in the description. Schema description coverage is 0%, and the description provides no help on how to use the parameter or its effect on output. The parameter is simple but description fails to add value.

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 explicitly states it checks the freshness of the Samsung Health export directory/CSVs, lists specific return values (mtime, days_since_export, is_stale flag, recommendation), and distinguishes itself from sibling tools by advising use before relying on other tools like samsung_health_daily_summary.

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?

Provides clear guidance: 'Use before relying on samsung_health_daily_summary or samsung_health_wellness_context' and defines stale conditions. Lacks explicit when-not-to-use or alternatives, but the context is sufficient.

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