kloakt_session_act

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

No annotations provided, so description carries full burden. Discloses state persistence and four actions, but does not mention error behavior, timeouts, or session lifecycle details beyond 'State persists.'

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?

Two sentences, front-loaded with key concept. Every word earns its place; no redundancy.

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 multiplexed tool with no output schema, description explains actions and parameter mapping adequately but omits return values or side effects (e.g., page content, confirmation). Leaves agent guessing about what the action returns.

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 coverage is 100% with individual parameter descriptions. Description adds value by mapping each action to its relevant parameters (e.g., 'For action=navigate: the URL'), clarifying which parameters apply when.

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?

Description clearly states it acts on a persistent session's page, multiplexes four actions. Distinguishes from sibling tools like session_open and session_read by being the driving tool.

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?

Explicitly states this is how you drive a session opened with kloakt_session_open, implying prerequisite. Could improve by noting when not to use (e.g., reading data via session_read), but context from sibling names provides differentiation.

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