gograph_session_create

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

Annotations declare readOnlyHint=true, implying no side effects, but the description states 'Start' and returns a session ID, which typically involves state creation. The description does not clarify this inconsistency, leaving ambiguity about actual side effects.

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 short, well-structured with clear sections (prerequisites, when/not, returns), and every sentence adds value. No filler.

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 good usage guidance, the contradiction between annotations and description undermines completeness. A simple tool with one optional parameter, no output schema, but the behavioral trait is unclear. Missing clarification on whether session creation involves persistent state.

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 coverage is 100% for the single optional parameter 'custom_word', and the description merely restates its purpose without adding new meaning. 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 verb 'Start' and resource 'telemetry audit session', with purpose 'tracking agent compliance and tool success metrics'. It distinguishes from sibling tools like gograph_session_audit, gograph_session_cleanup, and gograph_session_end by implying creation.

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 explicitly provides WHEN TO USE ('at the start of a multi-step coding task') and NOT TO USE ('when a session is already active'), offering clear context and exclusion criteria.

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