context

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are an aggregated digest drawn from several sources rather than raw records, which is useful, but with no output schema it says nothing about size, ordering or staleness of the aggregated brief.

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?

Two short sentences, front-loaded with what the brief contains and closed with the action directive. Every clause carries information; nothing is redundant.

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?

For a zero-parameter, read-only aggregator with no output schema, the description covers what the tool does and roughly what it returns. It leaves minor gaps around the scope of 'recent' and the ordering/size of the brief, but nothing that would block a correct first call.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no configuration is needed to invoke it.

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 concrete verb and resource ('One-page project brief') and enumerates the exact content it aggregates: goals, open tasks, accepted decisions, active ideas, recent log. That is specific enough to distinguish it from the log/recent/notes siblings, though it does not explicitly name or contrast against 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?

'Read this first' is an explicit entry-point instruction that tells the agent to call this before other tools, which is real usage guidance. It stops short of stating exclusions or naming alternatives (e.g. when to prefer recent or search), so it falls short of a 5.

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