autocode_session

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'persist state to file' and 'restore state from file,' which conveys the read/write nature, but it doesn't disclose important behaviors such as whether save overwrites existing files (destructive), file format specifics, error handling, or whether load creates the session in memory only. For a tool that mutates file state, this is a significant gap.

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?

Two sentences, zero wasted words. The description front-loads the purpose and immediately explains both action modes. Every phrase contributes meaning, and the action=... / action=... formatting is efficient and scannable.

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?

For a dual-mode tool with nested objects and no output schema, the description covers the two action modes adequately but leaves behavioral details unstated. It doesn't explain return values/output, file format expectations, or the consequences of missing state on save. The schema covers parameters well, but the description could add more about behavior for completeness given no annotations.

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?

Despite 100% schema coverage, the description adds meaning by mapping actions to behaviors ('save: persist state to file', 'load: restore state from file'), complementing the schema's enum descriptions. It clarifies the conditional requirement for state (save needs it, load doesn't). The description effectively reinforces and slightly enriches schema semantics.

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-resource pair ('Save or load an autocoding session') and explains both action modes explicitly. It distinguishes from siblings by focusing specifically on session persistence rather than autocoding execution or conversation. However, it doesn't explicitly differentiate from autocode_turn, which could also seem session-related.

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 explains the two action modes (save/load) and their purposes, which gives clear context for when each is used. However, it provides no guidance on when to use this tool versus the sibling tools (autocode, dialectic, autocode_turn), and no exclusions or when-not-to-use guidance. The relationship to these siblings is implied but not stated.

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