research_session_start

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that the tool both creates and updates a session and returns an identifier, which is useful. However, it does not explain how the create-vs-update decision is made (e.g., based on session_id), what happens to existing data, or any 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 a single efficient sentence that front-loads the core action and return value. It contains no waste, though it is too brief to carry the full explanatory burden for a tool with no annotations and no output schema.

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 tool with no annotations, no output schema, and several sibling tools operating on the same session concept, the description is incomplete. It does not clarify how session_id controls create vs update, how this tool relates to evidence_to_session or user_answer tools, or what the returned identifier should be used for.

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%, and the description does not mention original_query or session_id at all. The schema names and default provide some minimal meaning, but the description adds no parameter-level semantics beyond what is already in the schema.

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 a specific action ('creates or updates'), a clear resource ('SQLite research session'), and a return value (identifier). This makes the tool's purpose understandable and distinguishes it from siblings like research_session_understand_query or evidence_to_session tools, though it does not name a sibling explicitly.

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 gives no guidance on when to use this tool versus the sibling tools, and no conditions such as 'use when starting a new session' or 'use when updating an existing session'. The usage context must be inferred entirely from the tool name and sibling list.

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