memory_personal_review

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

With no annotations, the description must carry the behavioral disclosure burden. The wording 'Return ... dashboard' and 'review' imply a read-only, non-mutating operation, and the listed outputs suggest no side effects, but the description never explicitly states that it does not modify memory or whether any auth/rate constraints apply.

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?

A single, front-loaded sentence with no filler. Every phrase contributes: the output type, audience, and the four dashboard components are all stated efficiently.

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?

The output schema covers return shape, but the definition lacks parameter semantics and usage context. For a tool with no annotations and 0% schema coverage on parameters, the description is not enough to invoke it correctly with meaningful arguments.

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%, yet the description does not mention either parameter (limit or subject). The agent gets no help understanding how limit controls the dashboard or what values subject can take, making this a serious gap.

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 clear verb and resource: 'Return a user-facing personal memory review dashboard' with expected contents (counts, recent memories, conflicts, consolidation candidates). It does not explicitly compare against sibling tools such as memory_review_digest or memory_personal_list, so it falls just short of full differentiation.

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?

No guidance is given on when to choose this tool over the many overlapping siblings (memory_review_digest, memory_review_inbox, memory_conflicts, memory_stats). There are no usage conditions, exclusions, or alternatives, so an agent must infer the appropriate context.

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