get_daily_summary

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

No annotations are provided, and the description does not disclose behavioral traits such as whether data is available for future dates, what happens if no activity exists, authentication requirements, or rate limits. For a read tool, basic safety and error behavior should be noted.

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 short and direct, with a separate line for parameter documentation. It avoids unnecessary words, though it could be slightly more structured (e.g., listing returned metrics explicitly rather than in parentheses).

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?

Given the simplicity of the tool (one parameter, no nested objects), the description is mostly adequate. However, it lacks context on return value structure (though an output schema exists) and edge cases like invalid dates. Behavioral gaps lower the completeness.

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 sole parameter 'date' has no description in the input schema (0% coverage), but the description adds the format 'YYYY-MM-DD', which is meaningful guidance beyond the schema's type string. This addition helps the agent construct valid inputs.

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 retrieves a daily activity summary and specifies the metrics: steps, calories, distance, active minutes. This verb+resource combination is distinct from sibling tools like get_steps_data or get_activities which focus on different granularities or endpoints.

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 no guidance on when to use this tool versus the numerous sibling tools that also return activity data (e.g., get_activities_by_date, get_heart_rates). There are no exclusions, prerequisites, or context for appropriate use.

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