Review a period (week / month analytics)

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

Discloses key output components including a 'review_brief' for narration, but does not explicitly state that the tool is read-only or discuss any side effects. Without annotations, more explicit behavioral details would be beneficial.

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?

Four sentences packed with information—lists outputs, defaults, and range option—without unnecessary words. Efficient and well-structured.

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?

Covers what the tool returns (per-day data, rates, slippage, objectives, review_brief) and how to use it. Without an output schema, this description is adequate for an agent to understand the tool's purpose and output.

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 already covers both parameters with descriptions. The description reinforces the default 7-day range and adds context for using from/to for arbitrary ranges, adding value beyond schema.

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 provides 'Follow-up analytics across saved plans' and enumerates specific outputs (per-day rollups, completion rates, slippage list, objectives), making it distinct from sibling tools like read_plan or read_week.

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?

States default range (last 7 days) and how to specify a custom range ('pass from/to for a month or any range'), providing clear usage context. No explicit exclusions or alternatives, but the context is sufficient for typical use.

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