get_user_summary

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Get' and specifies the date format, but does not disclose authentication needs, data scope, caching, or side-effect profile. The 'compatible with garminconnect-ha' note is a compatibility hint, not behavioral transparency.

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 concise and front-loaded with the action, followed by a minimal Args section. It contains no filler, though it could add a little more context without becoming bloated.

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?

The output schema exists, so the return shape is covered. However, the description does not clarify what 'user summary' actually contains or when to use this tool over similar ones like get_stats or get_user_profile. This leaves the selection context incomplete.

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 only defines 'date' as a string with no description, so schema coverage is 0%. The description compensates by specifying the exact format 'YYYY-MM-DD', which is essential for correct invocation. This fully addresses the single parameter's semantics.

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 states a specific verb and resource ('Get user summary data'), making the core action clear. However, it does not differentiate this tool from numerous sibling get_* tools like get_stats, get_user_profile, or get_progress_summary_between_dates, so it lacks sibling distinction.

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?

No when-to-use guidance is provided, no exclusions are stated, and no alternative tools are mentioned. An agent has no basis for choosing this over similar summary/stats tools.

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