get_focus_stats

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

No annotations are provided, so the description must carry the burden for behavioral disclosure. It states that the tool defaults to today, which is also in the schema, but does not mention read-only behavior, timezone handling, data granularity, or any side effects. For a simple read tool, this is minimal.

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, direct sentence that front-loads the verb and resource. It avoids redundancy and is appropriately sized for a simple tool.

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?

For a tool with one optional parameter and no output schema, the description adequately lists the returned metrics (focus score, active time, productivity metrics) and the default behavior. It is not as complete as it could be regarding usage differentiation, but the tool's simplicity lowers the bar.

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 already provides 100% coverage for the 'date' parameter with format and default. The description restates the default but adds no new semantics beyond what the schema specifies. Baseline 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 the tool retrieves focus-related metrics ('focus score, active time, productivity metrics') from a specific source ('Daylens'). This distinguishes it from sibling tools like get_timeline (timeline events) and get_app_usage (app usage).

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 explicit guidance on when to use this tool versus siblings. The description only mentions a default date, but does not explain when to choose focus stats over timeline, app usage, search, or activity tools. Given multiple sibling tools, this lack of differentiation leaves the agent to guess.

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