session_context

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

Annotations are missing, so the description bears full responsibility for behavioral disclosure. It states the tool 'sets or gets' but omits side effects: overwrite behavior, persistence, value limits, or required permissions. For a mutation-capable tool, this is insufficient.

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, front-loaded sentence with no wasted words. It achieves conciseness, but could be expanded slightly to cover key details without losing efficiency.

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?

With no output schema, no annotations, and 0% schema coverage, the description is severely incomplete. It does not explain return values (for 'get'), error conditions, or behavior for missing keys. A tool with 4 parameters requires more contextual detail for correct invocation.

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 compensate. It mentions 'set or get' and 'shared context value', hinting at key and value roles, but does not explain each parameter explicitly. For 'action' it alludes to enum values, but nothing about 'value' being required only for 'set', or that 'key' is the identifier. The description adds minimal meaning beyond the raw 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 clearly states the tool's purpose: 'Set or get a shared context value within a session'. It uses a specific verb (set/get) and resource (shared context value). It distinguishes from sibling session management tools (create, join, leave, etc.) which deal with session lifecycle, not intra-session context.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., session must exist via session_create) or when to use get vs set. The action parameter implies usage, but the description lacks context for an AI agent to decide correctly.

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