mcp_engram_watch_workspace

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

Despite no annotations, description implies heavy resource usage ('power tier') and selective use, but lacks explicit details on side effects, lifecycle, or output behavior.

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?

Three concise sentences with no redundancy; first sentence conveys purpose, second gives alternative, third gives usage context.

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?

Adequately covers purpose, usage, and alternatives given the tool's simplicity; could clarify 'power tier' and 'deep mode' but not essential.

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?

Parameter is already fully described in schema (100% coverage); description adds no extra semantics about the path parameter.

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?

Description uses specific verb 'binds' and resource 'full-repo OS file-watcher', clearly distinguishing from sibling tools like mcp_engram_context_for_edit.

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?

Explicitly states when to avoid ('lean-avoid at wake') and when to use ('deep mode when passive daemon ingest is required'), and names alternative tool.

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