get_scores

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

No annotations are provided, so the description carries full burden. It discloses the return format (range, results, summary), date behavior (timezone, mutual exclusivity), and default date. Absent are potential error handling or access constraints, but the core behavior is well-covered.

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 about 5 sentences with bullet-like formatting for date options. It is efficient, scannable, and contains no redundant information.

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 complexity (5 params, date constraints) and an output schema, the description covers core functionality and return structure. Missing details include error messages, limits on days or date range, and explicit clarification that the tool is read-only (though implied).

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 description coverage is 0%, so the description must compensate. It fully explains each date parameter (date, start_date, end_date, days) with format, mutual exclusivity, and defaults. user_id is required but its purpose is obvious from the tool name.

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 starts with a clear verb+resource: 'Get scores for a user.' It distinguishes from sibling tools like get_sleep, get_biometrics, etc., by focusing on 'scores' and specifying date range behavior.

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 explains the three mutually exclusive date input options with formats and constraints, and mentions the default timezone. However, it does not provide guidance on when to use this tool over siblings like get_org_scores_summary or get_user_profile.

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