ck_context

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

No annotations provided, so the description carries full burden. It explicitly states 'Read-only', which is a key behavioral trait. It also explains the difference between compact and full detail levels, adding transparency. No mention of auth or rate limits, but for a read-only state fetch, this is adequate.

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 multiple sentences but each serves a purpose: listing contents, stating read-only, advising on detail_level, on session_id/project_root, and comparing with sibling. It is well-structured and not overly verbose, earning a 4.

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?

No output schema, but the description lists the components of the returned state (mission, budget, etc.), giving a good idea of what to expect. With 4 parameters and no required ones, the description sufficiently covers usage and behavior.

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%. The description adds meaning beyond schema: for detail_level, it explains compact vs full; for session_id, it mentions defaulting to active bound session; for project_root, it says it can resolve automatically. This enriches understanding, so score above baseline 3.

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 the tool fetches the full governed session state, listing many components (mission, budget, etc.). It distinguishes itself from sibling ck_context_pack by advising to use that tool for focused queries, thus providing specific verb+resource and differentiation.

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?

The description advises to call this tool at the start of every task and contrasts it with ck_context_pack for focused needs. It also provides guidance on when to use compact vs full detail_level, giving clear context.

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