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

Annotations supply only a title, so the description carries the behavioral burden and does disclose meaningful traits: what gets returned, that there is no persona to adopt, that identity must be preserved and referred to in the third person, and that the session must be woken per-agent. It does not state side effects, idempotency, or whether a session is allocated server-side — a notable gap for a bootstrap call with zero safety annotations.

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 imperative 'Call this first' and the payload enumeration are front-loaded, so the agent hits the critical instruction immediately. The host list (VS Code/Copilot, Cursor, Claude Code, Codex) is a dense enumeration that could be compressed, but every remaining sentence carries distinct information about identity handling or the recall alternative.

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, the description does the needed work by describing the shape of the response (identity, visible areas, permitted tools, keeper rules). Combined with the schema's session-ID guidance, an agent can call it correctly on first turn. The unexplained `scope` parameter is the main completeness hole.

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 coverage is only 50%: `kit_session_id` is documented in the schema itself (including the subagent rule) and the description adds nothing to it, while `scope` (work/personal/all) is neither described in the schema nor mentioned anywhere in the description. An agent cannot tell from either source what `scope` changes about the returned knowledge areas or tool list, and the description makes no attempt to compensate for that gap.

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?

States a concrete action (open Lady Whiskerdown) and enumerates the return payload (`you_are`, visible knowledge areas, permitted tools, keeper rules), which tells an agent exactly what a bootstrap call yields. It explicitly distinguishes itself from `recall` and implicitly from `areas`/`systems` by saying those are reported here. The metaphor 'an archive you can question' is slightly loose, but the concrete payload list removes ambiguity.

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?

Gives an unusually explicit trigger: call first in every new chat, before the first substantive answer, across named hosts. It also names the alternative for knowledge lookups ('call recall first instead of using general model knowledge'). There is no explicit when-not-to-call guidance (e.g. mid-conversation re-wakes or repeat calls in the same session), which keeps it below 5.

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