gograph_session_cleanup

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

The description says 'Delete' which contradicts the annotations readOnlyHint=true and destructiveHint=false. This is a serious inconsistency. While it adds context about returning deleted file count, the contradiction severely undermines transparency.

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 with clear sections: purpose, when to use, returns. Every sentence adds value without redundancy.

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 the tool's purpose, usage context, and return value adequately for a parameterless tool. However, the contradiction with annotations reduces reliability, and no output schema is provided, but that is not required.

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 in schema. The description adds meaning by explaining the tool's behavior and return value, which goes beyond the empty 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 the tool deletes stale inactive session telemetry JSONL logs, with a specific verb and resource. It distinguishes from sibling tools like gograph_session_audit, gograph_session_create, etc. by focusing on cleanup of stale logs.

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 when to use ('after auditing to keep the repository clean') and describes behavior when no session is active. Lacks explicit alternatives or when-not-to-use, but context is clear given sibling tool names.

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