session_context

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

Since no annotations are provided, the description carries the full burden. It discloses the tool's return contents and optimized format, which is helpful. But it does not state whether this is a read-only operation, mention side effects, or explain behavior around empty sessions or missing artifacts.

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 first sentence is front-loaded and useful. However, 'PRIMARY tool', 'GO-TO tool', and the repeated WORKFLOW POSITION section are redundant. The trigger bullets and workflow position overlap enough that some sentences do not earn their place.

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?

The description covers triggers, return content, and parameter semantics sufficiently for a simple read-style context tool. But there is no output schema, no annotations, no behavior around stale/missing state, and no guidance on how this tool relates to siblings like check_context or session_statistics. The default value mismatch also reduces completeness.

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 explains all three parameters in plain language, which is important because schema description coverage is 0%. However, it states max_messages default is 20 while the schema states default is 5. This conflicting default can mislead an agent into assuming different behavior, so the parameter guidance is partially inaccurate.

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 states a specific verb and resource: 'Get a compiled context view of the session.' It also clarifies what is returned (summary, messages, state, tasks, artifacts) and claims PRIMARY status. It does not explicitly differentiate against close siblings such as check_context or get_session_state, but the compiled-view framing is distinct enough.

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 clear AUTOMATIC TRIGGERS and WORKFLOW POSITION guidance, telling the agent when to call it: after joining, before starting work, after task assignment, and when unsure. It gives strong context but no when-not-to-use statements or named alternatives.

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