phantomswap_create_session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the mapping format but does not explain what happens when a session is created, whether it persists, how naming collisions are handled, or what the response contains. This is a significant transparency gap.

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 two sentences with no filler. The essential example for the most complex parameter is front-loaded, making it quick to parse.

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 four parameters and no annotations, this description is incomplete. It covers the mappings parameter well but omits semantics for the other required parameters and any context about session creation behavior. An agent would likely need to guess at several details.

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 provides a helpful example for 'mappings', but leaves 'name', 'description', and 'case_sensitive' semantically unexplained beyond their schema titles and default value.

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 states a specific verb and resource: 'Create a new swap session with key-value mappings.' This clearly distinguishes it from sibling tools like phantomswap_list_sessions or phantomswap_mask_text. The purpose is immediately understandable.

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 verb 'create' implies when to use it, but there is no explicit guidance about when to choose this over alternatives, no preconditions, and no mention of what a 'swap session' is used for afterward. The context is inferable but not stated.

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