connectCesiumMap

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

Annotations declare readOnlyHint=false and destructiveHint=false, telling the agent this is a non-destructive but state-changing operation. The description adds nothing beyond that: no statement about whether connecting mutates existing session state, what happens on failure, or whether connections are exclusive.

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?

It is short, but brevity here is under-specification rather than efficiency. The one clause present ('Internal map app transport') spends the whole budget on a vague framing instead of the information an agent needs.

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 state-changing connection tool in a family of session-lifecycle siblings, with an undocumented required parameter and no output schema, the description provides almost nothing an agent needs to invoke it correctly or recover from errors.

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% for the single required parameter, sessionId, so the description needed to explain what a session id refers to and where it comes from. It says nothing, leaving the only parameter entirely uninterpreted.

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 restates the tool name ('connect') and adds only the vague qualifier 'Internal map app transport', which doesn't say what is being connected to (a session? a running map instance?) or what the call establishes. It fails to distinguish itself from siblings like openCesiumMap, exchangeCesiumMap, and 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?

No indication of when to call this versus openCesiumMap or exchangeCesiumMap, nor any prerequisites (e.g., whether a session must already exist). 'Internal' hints at restricted use but gives an agent no actionable selection criteria.

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