exchangeCesiumMap

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the description does not need to establish safety basics. However, it adds no behavioral context at all: it does not explain what is being exchanged, how sessionId and token are used, or how the optional results array affects behavior.

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 six-word fragment with no front-loaded explanation of action, scope, or return behavior. It is concise only because it is severely under-specified, not because it efficiently conveys required information.

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 transport/mutation tool with three parameters, a required sessionId and UUID token, an optional nested results array, no output schema, and no annotations explaining side effects, the description is completely inadequate. An agent cannot determine what the tool actually does or how to use its parameters from this text.

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, but it mentions none of the three parameters. It says nothing about token, sessionId, or the nested results array with id/error/result entries, leaving all parameter semantics to the bare 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 phrase "Internal map app transport: exchange" largely restates the tool name rather than naming a specific action or resource. It gives a domain hint (map app transport) but does not distinguish this tool from close siblings such as connectCesiumMap, openCesiumMap, or disconnectCesiumMap.

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?

There is no guidance on when to call this instead of connectCesiumMap/openCesiumMap/disconnectCesiumMap, nor any stated preconditions or exclusions. The only context is "internal," which does not help an agent choose among alternatives.

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