cabinet_wake

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

With no annotations, the description carries the behavioral burden and discloses useful traits: codeword validation, ingestion of status_block.md and last_session.md, a <250 token budget, DUMEdb state checking, and a tight briefing return. It does not explain failure behavior, invalid-codeword handling, or whether it mutates any state.

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 is front-loaded with the critical mandatory instruction and then lists the operational sequence. It is slightly repetitive with emphasized 'MANDATORY' and 'DO NOT' phrasing, but each sentence supports correct invocation.

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?

For a mandatory session-bootstrap tool with an output schema, the description provides enough context: when to call it, what it ingests, what it checks, and what it returns. Remaining gaps are around error handling and side effects, which are not fully covered without annotations.

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?

There is one optional codeword parameter with a schema default, but schema description coverage is 0%. The description says the codeword is validated and references 'box is the game' as a trigger phrase, but it does not define valid values, format, requiredness, or the effect of an invalid codeword.

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 specific initialization operation: executes the Wake Handshake, validates a codeword, ingests compass files, checks DUMEdb state, and returns a briefing package. It clearly distinguishes this bootstrap action from sibling tools by forbidding filesystem searches and other actions until it runs.

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?

It gives explicit timing and trigger conditions: every new session, greetings, status requests, 'catch me up', 'wake', 'start', 'briefing', and the phrase 'box is the game'. It also states a clear exclusion: do not search the filesystem or take other actions until this tool has executed.

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