gograph_session_create

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

Description aligns with annotations (mutating, non-idempotent) and adds specific behavioral details: writes session state under .gograph/sessions and returns structured message with session ID. No contradictions.

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?

Extremely concise (5 sentences) with clear structure: purpose, behavior, prerequisites, usage guidance, return value. Every sentence earns its 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?

Despite no output schema, description explains return value. Covers prerequisites (none), behavior, and usage context. Fully sufficient for a simple creation tool.

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?

Schema description already covers the sole parameter (custom_word). Description merely restates it without adding new information. With 100% schema coverage, 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?

Description clearly states verb ('Start'), resource ('telemetry audit session'), and purpose ('tracking agent compliance and tool success metrics'). Differentiates from siblings like gograph_session_end and gograph_session_cleanup.

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 provides WHEN TO USE and NOT TO USE guidance. Tells agent to call once at start of multi-step task and warns against calling when session already active.

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