brief

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

With no annotations, the description carries the full burden, and it does so well by itemizing what the brief surfaces (requests/files/tokens, cut-off or failing work, regressions, suspicious changes). It doesn't explicitly state it's a read-only report or note any limits, but for a read-only aggregation tool the content disclosure is the substantive behavioral trait.

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 core sentence is front-loaded and dense but well-organized via a colon-led list of the four report sections. The trailing two sentences largely duplicate the schema's parameter descriptions, which is minor waste.

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?

No output schema exists, so the description must convey return content — and it enumerates the brief's sections, time windows, and default scope thoroughly. An agent has everything needed to call it and understand what comes back.

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 100% and both parameters are fully documented in the schema, including the `period` enum semantics. The description restates the same `period`/`project` defaults rather than adding syntax or edge-case meaning beyond the schema, so the baseline of 3 applies.

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?

States a clear resource (a per-project brief/recap) and enumerates its four content categories (what agents did, what's unfinished, what's failing, what's worth a check), so the agent knows exactly what it returns. However, it does not distinguish itself from close siblings like `recap`, `today`, or `report_card`, which sound like overlapping reports.

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 'morning brief or weekly recap' framing and the `period`/`project` defaults imply when it's useful (daily/weekly review, all projects by default), but there is no explicit when-to-use guidance or reference to the alternative siblings (`recap`, `today`, `test_status`). Usage must be inferred.

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