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

The annotations contain only a title, so the description carries the burden. It discloses non-obvious behavior: the `you_are` identity is offered, not imposed, and the agent may answer as itself while reading Lady Whiskerdown's archive. It does not explicitly state read-only/side-effect status, but the 'returns/reading archive' language implies a read-only initialization.

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 most important instruction, 'Call this FIRST,' followed by what it returns and how to handle identity. It is slightly wordy with client names and flavor text, but every sentence contributes to the agent's decision-making.

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 no output schema and minimal annotations, the description covers when to call, what it returns, identity handling, and the relationship to recall. It does not explain the exact output structure or the `scope` behavior, but the session-ID parameter is documented in the schema and the core context is present.

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 description coverage is 50%, and the description adds no explanation of `scope` or `kit_session_id`. The `kit_session_id` parameter is already well documented in the schema, while `scope` relies on its enum. The description's reference to return fields does not clarify parameter usage, so it stays at baseline.

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 names the operation explicitly: call this first in every new chat and it returns Lady Whiskerdown's identity, visible knowledge areas, permitted tools, and the working contract. This is a specific initialization/context-loading purpose, clearly distinct from sibling tools like recall or remember.

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: 'Call this FIRST in every new chat' and 'before the first substantive answer.' It also routes knowledge lookups toward recall instead of general model knowledge. It does not enumerate exclusions or differentiate from every sibling, so it stops short of a 5.

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