civil3d_session

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

No annotations are provided, so the description carries full burden. It discloses key behaviors like the lifecycle (begin, execute, commit, abort) and that execute does not commit. However, it does not mention potential destructiveness of commit/abort, prerequisites, or side effects. Adequate but not thorough.

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 two sentences, front-loaded with the purpose, then listing the actions. Every sentence is necessary and no words are wasted. Highly concise and well-structured.

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 complexity (5 parameters, session lifecycle, no output schema), the description covers the main user flow and action semantics. However, it omits details like error handling, timeouts, or prerequisites (e.g., need to be in a Civil 3D environment). Still, it is largely complete for a session management 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 coverage is 100%, so the baseline is 3. The description adds context about actions (e.g., 'execute for each script step (no commit)') but does not elaborate on parameters like code, sessionId, or confirmed. The value added is marginal.

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 'Manage' and the resource 'multi-step Civil 3D script sessions', distinguishing it from sibling tools like civil3d_execute and civil3d_command. It provides specific actions (begin, execute, commit, abort) and their purposes, making the tool's function unambiguous.

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 states it is 'useful for complex workflows that need multiple code steps in one transaction', implying when to use it. However, it does not explicitly mention when not to use it or name alternatives, though sibling tool names provide some context. A clearer exclusion would improve the score.

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