report_weekly

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

With no annotations, the description carries the burden of behavioral disclosure. It describes the report content but does not explain side effects, permissions, or whether the operation is read-only. The term 'generate' could imply creation but no mutation is clarified.

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 concise sentence that front-loads the tool's purpose and output structure. Every element (weekly report, daily grouping, category summary, total minutes) 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?

The high-level output structure is covered and an output schema exists, but the description lacks essential parameter context and usage scope. It does not address how the weekly range is determined or what start_day means.

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%, and the description does not mention start_day at all. The agent receives no guidance on the parameter's format, meaning, or default behavior, leaving invocation ambiguous.

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 generates a weekly report with specific aggregations (per-day completion count, category summary, total work minutes). The 'weekly' scope distinguishes it from the sibling tool report_daily.

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 implies the tool is for weekly reporting but does not provide explicit guidance on when to choose it over report_daily or how to handle the start_day parameter. No alternatives or exclusions are mentioned.

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