efficiency_report

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

No annotations are provided, so the description carries the full burden. It discloses that the tool analyzes and detects gaps but does not state read-only behavior, required permissions, side effects, or return value structure. The existence of an output schema partially mitigates this, but the description itself adds insufficient behavioral context.

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 concise and well-structured: a one-sentence purpose, a succinct list of capabilities, and parameter details. Every sentence adds value, and the key information is front-loaded.

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 output schema exists (so return value explanation is not needed), the description is mostly adequate but lacks information on prerequisites, error conditions, or how gaps are identified. It covers the main functionality but has room for improvement.

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 description includes an 'Args' section specifying the format (YYYY-MM-DD) for both start_date and end_date, which adds meaning beyond the schema's simple string type. Schema coverage is 0%, so this extra detail is valuable. However, it does not explain constraints (e.g., date range limits) beyond format.

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?

Purpose is clearly stated: 'Analyze time distribution and detect gaps between entries.' It specifies the verb and resource and distinguishes from siblings like time_summary or billing_report by highlighting gap detection and daily breakdowns.

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?

Only an implied usage ('Useful for finding productivity patterns') is given. No explicit guidance on when to use versus sibling tools like time_summary or billing_report, nor any conditions or exclusions.

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