invariance_kb_session_create

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

Annotations already mark this as non-read-only, non-destructive, and open-world; the description's 'Create' is consistent with that. It adds the behavioral context that the session is multi-turn and KB-scoped, but does not disclose side effects, return shape, or session-lifetime details.

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 concise sentence with no filler; the core verb, resource, and scope are front-loaded. It is appropriately sized for a simple create operation.

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 two-optional-param create tool with no output schema, the description gives the essential purpose but leaves parameter semantics and return expectations undocumented. Sibling context plus annotations reduce risk, but an agent still has to guess what a successful response contains.

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 names neither 'model' nor 'title'. The agent gets no help understanding what model identifier or title value to supply, and the optionality of both parameters is not explained.

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?

States a clear verb ('Create') and a specific resource ('multi-turn ask session for the agent KB'). It anchors the tool to the KB session family among many sibling tools, though it does not explicitly differentiate from invariance_session_create.

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 implies the use case: creating a multi-turn ask session against the agent KB. It gives no explicit when-to-use guidance or exclusions, and with siblings like invariance_session_create and invariance_ask nearby, the agent must infer the boundary.

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