memory_task_context

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add a real behavioral constraint: only explicitly tagged durable user/project reminders are returned and other task facts are stripped. It still does not describe the "SMC/1" serialization format or what token_budget does to the output, which are the traits most likely to surprise a caller.

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?

It is a single front-loaded sentence with no padding, and the inclusion/exclusion clause is placed where it matters. The one waste is the unexplained "SMC/1" token, which consumes space without informing the reader.

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?

With no output schema and zero parameter documentation, the description needed to explain the return shape and budget semantics itself, and it does not. Key facts for correct invocation — what SMC/1 output looks like, how token_budget truncates it, and what project_root must point at — are all missing.

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% across three parameters, so the description carries the full burden and fails to meet it. It gives no meaning for project_root, task_id, or token_budget (including its 128–100000 range and truncation behavior). Only a vague implication that exactly one task is targeted can be inferred.

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 names a specific verb and resource ("Read one open task"), so the basic operation is identifiable. However, it never distinguishes this from the sibling memory_open_task, which by name appears to read open tasks as well, and the opaque token "SMC/1" is not explained. An agent cannot confidently tell which of the two reading tools to pick.

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?

There is no statement of when to use this versus memory_open_task, memory_task_checkpoint, or memory_recall. The only scoping signal is negative ("other task facts are excluded"), which hints at a narrow payload but does not tell an agent what situation calls for this tool.

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