session_complete

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

No annotations are provided, so the description must fully disclose behavior. It mentions auto-save behavior and the 'require_target_match' flag with warning, but does not clarify if the session ends, what gets saved, or whether further operations are allowed. The side effects of completing a derivation are not fully described.

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 structured with a concise one-line purpose followed by an Args block. However, it is somewhat lengthy for a simple completion action. It could be more front-loaded and trimmed, but the structure is clear.

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 8 parameters, no annotations, and an output schema (assumed rich), the description covers parameter purpose but lacks overall process context. It does not explain prerequisites, return value structure, or what 'completing the derivation' entails. The behavioral gaps leave the agent underinformed.

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 0%, so the description must compensate. It provides a brief one-line explanation for each parameter (e.g., 'Formula description (physical/mathematical meaning)'). However, these explanations are shallow and do not include constraints, formats, or examples. Some parameters are just listed by name.

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 states 'Complete the derivation and auto-save' which clearly indicates the tool's purpose. It lists parameters and their meanings, distinguishing it from sibling tools like session_abort or session_rollback. However, it does not explicitly differentiate itself from similar session finalization tools.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., a session must be active) or contrast with siblings like session_abort or session_save (which doesn't exist as sibling). Usage context is only implied by the tool's name and parameter names.

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