prepare_task_dream

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

Without annotations, the description discloses several behavioral traits: it modifies SKILL.md and receipt.json only when persist=true, never modifies AGENTS.md or CLAUDE.md, performs prompt-injection scanning, and notes that recalled text is evidence not authority. This goes beyond basic expectations.

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 starts with a clear purpose statement and uses a structured Args list. Each sentence adds value, though the paragraph could be slightly more concise. Overall efficient and well-organized.

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?

Given the tool's complexity, absence of annotations, and presence of an output schema, the description adequately explains purpose, parameters, side effects, and safety. It covers what is needed for an agent to use 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?

The description adds significant meaning to all four parameters beyond the input schema. For example, task is 'the concrete task', agent_id is 'MemoryOS identity used for scoped recall', token_budget specifies range 256-8000, and persist explains file writes. Schema coverage is 0%, so the description fully compensates.

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 clearly states the tool prepares an expiring, receipt-backed task skill before agent work. It explains the capsule combines memory and recall, distinguishing it from siblings like recall_relevant or vault_write_action, though it does not explicitly contrast 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?

The description indicates use 'before agent work' and explains the tool is for preparation, but does not explicitly state when not to use it or provide alternatives. Some guidance is given but not comprehensive.

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