generate_weekly_summary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says a summary is generated; it does not clarify whether this is read-only, how the past week is calculated, whether it aggregates across all conversations or only certain types, or what data the summary contains.

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, tight sentence that front-loads the core purpose without wasted words. However, its brevity comes at the cost of omitting useful parameter and behavior details, so it is concise but slightly under-specified.

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?

Although the tool is simple and has an output schema, the description leaves the meaning of week_offset undefined, which is essential for correct invocation. An agent cannot determine how to request the desired week without additional assumptions, so the description is not complete enough on its own.

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 only parameter, week_offset, is not mentioned in the description at all. The schema provides its name, title, type, and default, but not what the offset means (e.g., 0 = current week, 1 = previous week) or how it relates to 'past week'. With 0% schema description coverage, the description needed to compensate and does not.

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 states a specific action ('Generate') and resource ('a summary of conversations') with a time constraint ('past week'). This distinguishes it from the sibling search/add/update/get tools as an aggregation operation, though it does not explicitly contrast it with any of them.

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 phrase 'past week' implies the tool is appropriate when a weekly summary is needed, but the description provides no explicit guidance on when to use this tool versus search_conversations or search_by_topic. No exclusions or alternative conditions are given.

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