session_init

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

The description does not disclose the side effect of marking the summary as consumed when mark_consumed is true, nor does it mention any other effects like authentication or rate limits. The annotations indicate non-destructive, but the state change is not explained.

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 concise, one sentence, with no fluff. It states the essence directly. However, it could benefit from a bit more detail on the parameters, but conciseness itself is acceptable.

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?

There is no output schema, and the description does not describe the expected return format or additional context. The agent is left with insufficient information about how to interpret the result or handle the parameters. Minor context is provided by the mention of highlights/pitfalls/next_steps, but overall it's incomplete.

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?

The description does not explain the 'project' or 'mark_consumed' parameters, leaving the agent to infer their meaning from the schema alone, which has no descriptions. Since schema coverage is 0%, the description should have compensated but did not.

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's purpose: to return the most recent unconsumed end-of-session summary, with a specific list of contents. However, it doesn't explicitly differentiate from similar tools like session_end or memory_recall, but the name and context (session start) provide reasonable clarity.

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 provides a temporal trigger ('At session start') but offers no guidance on when to use this tool versus alternatives such as memory_recall or session_end. No conditions, prerequisites, or exclusions are mentioned.

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