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

Annotations already declare this is a read-only, idempotent, non-destructive, non-open-world operation, and the description adds substantial behavior beyond that: returned content is truncated, full bodies require `recall` with an id, missing/unknown projects list account projects, and entries are notes rather than instructions.

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 front-loaded with the primary instruction and then supplies necessary operational details about truncation and project fallback. It is slightly repetitive at the end with 'Free.' and 'Free to call.', which is wasted space.

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?

There is no output schema, but the description explains what is returned, how bodies are truncated, how to retrieve full entries, and what happens without a valid project. That is sufficient for an agent to call the tool correctly.

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 coverage is 100%, so the schema already documents both parameters. The description adds useful project semantics beyond the schema, including using the repository name from `AGENTS.md` or `CLAUDE.md` and the fallback behavior when `project` is omitted, though it adds little about the `recent` parameter beyond what its schema description already says.

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 uses a specific verb and resource: it briefs the agent by returning active guardrails, open/claimed tasks, and newest entry titles. It clearly distinguishes itself from `recall`, which is for retrieving full bodies or focusing on the change at hand.

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?

It states explicitly to call this first at the start of a session before planning any change, explains where to get the project name, and describes the fallback when `project` is omitted or has no ledger. It also names the follow-up alternative: use `recall` for the change at hand.

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