ck_context

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

Declares 'Read-only' explicitly, which discloses the primary behavioral trait. Without annotations, the description carries the burden, and it sufficiently conveys no side effects. Could mention logging or other transparency, but the read-only disclosure is clear.

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 well-structured with clear front-loading of purpose, followed by usage details and alternatives. Every sentence adds meaningful information without redundancy, given the tool's complexity.

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 tool that fetches comprehensive state, the description covers all key aspects: what it returns (list of components), control over detail_level, session identification, and a usage directive. No output schema, but the return value is well described.

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 100%, so baseline is 3. The description adds value by explaining defaults for detail_level and session_id, and the role of project_root, going beyond the schema definitions.

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 clearly states it fetches the full governed session state and lists specific components (mission, budget, etc.). It distinguishes itself from the sibling tool ck_context_pack by noting the full snapshot vs. focused bundle.

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 instructs to call at the start of every task to reacquire state, and provides alternative (prefer ck_context_pack for focused bundles). Also gives guidance on detail_level and session_id defaults.

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