get_user_summary

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

With no annotations, the description bears full responsibility for behavioral disclosure. It lists returned metrics but does not mention data freshness, authentication requirements, rate limits, or error handling for invalid dates. The phrase 'and more' is vague and incomplete.

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 a single sentence that front-loads the purpose. It is efficient, though the trailing 'and more' is vague and could be replaced with specifics.

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 no output schema, the description should clarify the return structure. It only mentions a few metrics and ends with 'and more', leaving ambiguity. Among many similar sibling tools, more distinction is needed.

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% for the single parameter 'date', which is described in the schema as 'Date in YYYY-MM-DD format (required)'. The description also notes 'for a specific date', aligning with the parameter but adding no new semantic detail beyond the schema.

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 comprehensive user activity summary for a specific date, listing metrics like steps, calories, distance, and active minutes. It specifies the verb 'Get' and resource 'user activity summary', and distinguishes it from more specific siblings by emphasizing comprehensiveness, but does not explicitly differentiate from 'get_daily_summary' or 'get_health_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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or exclusions. The description only states what the tool does, leaving the agent without context for appropriate selection.

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