session_show

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool shows state and formula, and includes a warning about post-derivation usage. However, it does not mention side effects, permissions, or whether it is read-only. The description is adequate but not exhaustive.

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 highly concise: three short sentences. The first states purpose, the second is a critical usage warning, the third describes the parameter. No wasted words, and the important instruction is front-loaded.

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 tool's simplicity (one optional boolean parameter) and the presence of an output schema, the description provides sufficient context. It specifies the tool shows current derivation state and formula, and includes a necessary usage warning. The sibling tool set is large, but the description distinguishes it adequately.

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 add meaning beyond the input schema. It explains the 'show_steps' parameter as 'Whether to show all step history', which adds context not present in the schema's title. The explanation is clear and helpful.

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 tool shows the current derivation state and formula, with a specific verb and resource. Among many session-related siblings, this distinguishes it by focusing on the current state and formula, not listing steps or status.

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 explicitly states it 'Must be called after each derivation operation to show the user the result!', providing clear guidance on when to use it. It does not explicitly list alternatives or when not to use, but the imperative is strong and contextually complete.

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