Get Session Token

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

The annotations only provide false hints for readOnly, idempotent, and destructive, leaving the description to explain behavior. It does so by disclosing that the token is a fresh UUID4, that it scopes per-session cache, and that cache validity ends when any vault document is updated. This adds meaningful behavioral context without contradicting annotations.

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 three sentences, each with a clear role: generation, usage instruction, and cache validity. No wasted words; all information is front-loaded and directly relevant. It is exceptionally concise while covering purpose and usage.

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 that there are no parameters and the tool relies on an output schema (not shown), the description covers the essential context: what the token is, how to use it, and when it becomes invalid. It leaves no significant gaps for the agent's decision-making.

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?

The tool has zero parameters, so the schema is trivially complete. The description correctly mentions no parameters but explains how the return value should be used (passed as session_token), which is useful additional semantics. Baseline for 0 params is 4, and the description meets it.

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 function: 'Generate a fresh session token (UUID4) for use with vault_inject / vault_prime.' This is a specific verb (generate) with a concrete resource (session token) and its intended downstream use, distinguishing it from sibling tools like vault_link_session or vault_get_server_info.

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 instructs when to use the token: 'Pass the returned token as session_token in subsequent injection calls' and ties the usage to vault_inject/vault_prime. It provides clear context for why this tool is needed (scoping cache to a conversation), effectively guiding the agent on when to call it relative to other tools.

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