week_overview

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

No annotations exist, so the description must carry the burden. It notes that multi-value filters accept both a list or single string, which helps. However, it does not disclose other traits like read-only nature, performance, or error behavior.

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 very short (3 lines plus metadata) and is front-loaded with the core purpose. It is concise but could be more detailed without being verbose.

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 11 parameters, 0% schema coverage, no output schema, and no annotations, the description is severely incomplete. It fails to explain return structure, parameter defaults, or behavior for missing data.

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?

With 0% schema description coverage, the description should compensate but only explains that multi-value filters accept a list or single string. It does not clarify other parameters like local_date, days, text_query, or limit_per_section.

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 returns a planning-oriented overview split into events, due tasks, and overdue tasks. This specific verb-resource combination distinguishes it from siblings like week_agenda or upcoming_tasks.

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 mentions related tools in brackets but provides no explicit guidance on when to use this tool versus alternatives. It lacks context on prerequisites or exclusions.

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