gograph_session_end

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

The description states that the tool writes logs and ends the session, implying a write operation. However, annotations indicate readOnlyHint=true, contradicting this. This inconsistency undermines transparency, as the agent cannot reliably infer whether the tool modifies state.

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 with three sentences, front-loaded with the action. Every sentence adds value: purpose, usage guidance, and return value. No extraneous words.

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 zero parameters, the presence of annotations, and no output schema, the description covers all necessary information: what it does, when to use, when not to use, and expected return. It is fully complete for the tool's simplicity.

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 tool has zero parameters, so the schema coverage is 100%. The description does not add any parameter information because none exist. Baseline 3 is appropriate.

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 action: 'End the active telemetry session cleanly and write end-of-session logs.' It specifies the verb (end), the resource (active telemetry session), and additional detail (write logs). This distinguishes it from sibling session tools like gograph_session_create or gograph_session_audit.

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 explicit usage guidance: 'WHEN TO USE: Call once after you have completed all edits and post-edit reviews. NOT TO USE: When no session is active.' It also mentions no prerequisites, giving clear context for appropriate use.

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