get-daily-summary

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

No annotations provided, so the description carries full burden. It lists the metrics returned but does not disclose behavior like authentication needs, error conditions, or whether it returns a single object or array. The input schema adds default date behavior, but behavioral context is lacking.

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?

A single sentence front-loads the purpose and lists key metrics without extraneous information. Every word earns its place.

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 tool's simplicity (one optional parameter) and many siblings, the description is minimally adequate. It explains the output but omits specifics on structure or date range. No output schema amplifies the gap.

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 the 'date' parameter well-described in the schema. The description adds no additional semantic value beyond the schema's 'YYYY-MM-DD, defaults to today', so baseline score of 3 is appropriate.

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 it retrieves a daily summary of steps, calories, distance, etc., using the verb 'Get' and resource 'daily summary'. However, it does not differentiate from sibling tools like get-daily-heart-rate or get-daily-intensity-minutes, which focus on single metrics.

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 guidance on when to use this tool vs. alternatives. With many sibling tools for specific daily metrics, the description should indicate that this tool provides an aggregate overview, but it does not.

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