session_state

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

No annotations provided, so description fully bears transparency. It details the output structure (current_shape metrics, named objects, snapshot names, variables summary) and implies read-only behavior with 'snapshot' language. Though no explicit read-only statement, the description is sufficiently transparent for a zero-parameter reporting tool.

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?

A single sentence that front-loads the purpose and output, uses concise language, and includes all essential information without 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 the tool's simplicity (no parameters, clear output), the description fully covers what the tool does, its return content, and when to use it. The existence of an output schema is supplemented by description details, making the definition complete.

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 input schema has zero parameters, and description adds no redundant parameter info. Per rubric, baseline is 4 for zero params. Description does not miss any parameter details since none exist.

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 returns a structured JSON snapshot of the current session, listing specific elements (shape metrics, named objects, snapshot names, variables summary). It distinguishes itself from sibling tools by mentioning it replaces list_objects and is used for orientation after reset/restore/build.

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 advises to 'use this to orient after a reset, restore, or multi-step build'. Provides specific usage context (confirming active geometry and variables) and names an alternative (list_objects) that it replaces, guiding the agent on when to select this tool.

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