ck_session_digest

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

The description adds behavioral context beyond annotations: it explains that generate creates a new digest, latest returns the most recent, and list provides paginated history. Annotations (readOnlyHint=false, destructiveHint=false) are consistent; no contradiction.

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 two sentences with no wasted words. First sentence summarizes purpose and content; second sentence lists modes and use case. Efficient and front-loaded.

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 the tool has 3 parameters (2 with enums) and an output schema exists, the description provides sufficient context: it explains modes, output type (condensed digest), and mentions pagination for list mode. The presence of an output schema covers return value details.

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%, and the description adds value by explaining the three modes and their purposes (e.g., 'create a new digest', 'return the most recent', 'paginated history'). This supplements the enum descriptions in the schema.

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 generates a condensed, human-scannable digest of session activity, listing specific components (tasks, findings, budget, etc.) and three modes. This distinguishes it from sibling tools like ck_session which likely provides raw session data.

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 explains the tool is designed for a quick summary without reading raw event streams, implying when to use it. It does not explicitly mention alternatives or when not to use, but the context is clear enough for an agent.

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