gograph_session_cleanup

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

Adds context beyond annotations: behavior when no session is active, no prerequisites, and return value. Annotations already indicate destructive and idempotent, but description enriches understanding.

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?

Very concise: two sentences plus structured 'WHEN TO USE' and 'RETURNS' sections. No wasted words, front-loaded with the action.

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?

Complete for a zero-parameter tool with no output schema. Describes behavior, condition, prerequisites, and return value. Adequate for an AI agent to select and invoke correctly.

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?

No parameters exist; schema coverage is 100% trivially. Description does not need to add param info. Baseline score of 4 applies for zero-parameter tools.

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 'Delete all stale inactive session telemetry JSONL logs' with clarification on behavior when no session is active. This distinguishes it from siblings like gograph_session_audit, gograph_session_create, and gograph_session_end.

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?

Explicitly states 'Call after auditing to keep the repository clean', providing clear context for when to use the tool. Does not mention when not to use or alternatives, but sufficient for a cleanup task.

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