Weekly summary

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so safety profile is clear. Description adds behavioral context: 'local intake totals' and 'seven days', which is useful beyond annotations. No contradictions.

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?

Single sentence with zero waste. Verb 'Summarize' front-loads the action. Appropriate length 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?

Given the tool is a simple read-only summary with good annotations, the description covers the basic purpose and time range. However, it lacks details on what the summary contains (e.g., calories, nutrients) and the output format. Since no output schema exists, more description would be helpful.

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%. Description only mentions 'start date' indirectly but does not explain the meaning or format of start_date or the purpose of response_format. With two parameters, the description adds limited value for one parameter and none for the other.

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?

Description clearly states it summarizes seven days of local intake totals from a start date. The verb 'summarize' and specific resource 'local intake totals' with time range 'seven days' clearly distinguishes from sibling tools like daily_summary (one day) or carbon_summary (carbon focus).

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?

Description implies usage when a weekly summary is needed but provides no explicit guidance on when not to use or alternatives among sibling tools. No exclusions or context for selection.

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