session_variables

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

The description advertises a 'clear' mode that destroys saved session state, while annotations declare readOnlyHint=true. An agent trusting the annotation could call with clear=true believing the operation is side-effect free, so the description and structured metadata conflict on the safety profile. The masking detail is useful, but the contradiction dominates.

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 sentence, front-loaded with the primary action, that names both operating modes and the source of the data with zero filler.

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?

An output schema exists, so return values need not be described, and the masking note covers a key concern. But for a tool with a state-destroying mode, the description says nothing about whether clearing is permanent, session-scoped, or what remains afterward, leaving a meaningful gap.

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?

With one parameter at 0% schema coverage, the description carries the burden and does so: it distinguishes the two modes (default show-and-mask vs. clear) that map directly onto the boolean 'clear' flag. It stops short of stating that clear=true is destructive/irreversible or that masking is the default when the flag is omitted.

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 pairs two concrete verbs (show/clear) with a specific resource (session variables) and traces their origin to the 'extract' feature of soap_call/rest_call, which no sibling tool covers. An agent can tell what this does without opening the schema, though it never explicitly contrasts itself with check_last_response or the call 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 mention of variables 'saved by extract on soap_call / rest_call' implies the situation in which an agent would want this tool (inspecting values captured from a prior call). However, there is no explicit statement of when to prefer it over check_last_response, nor any prerequisite such as 'call soap_call with extract first' stated as a condition.

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