mcp_engram_session_start

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

With no annotations, description fully discloses default bundle behavior, references alternative for full harness, and warns against specific actions. However, does not explicitly state side effects like destruction or authorization needs.

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?

Single dense paragraph with no wasted words. Front-loads mandatory nature, each sentence adds value: bundle details, alternatives, action sequence, warnings, doc references.

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?

Covers mandatory first-call context, default behavior, and next steps. References external docs for deeper detail. Lacks return value explanation but no output schema exists.

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 has 100% coverage with clear descriptions. Description adds context like default bundle settings and explains purpose of include_spatial (inline ingest), enhancing understanding beyond schema.

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 clearly states it's the 'MANDATORY first MCP call every session', specifies it provides a slim bundle, and distinguishes from sibling mcp_engram_get_continuation_bundle for full harness.

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 says when to use (first call), provides step-by-step actions (execute suggested actions before edits, ack with mcp_engram_ack_wake_queue), and warns against calling watch_workspace at wake.

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