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

No annotations are provided, so the description carries the behavioral burden. It does disclose that view links are read-only, which is useful behavioral context about loading constraints. However, it doesn't disclose what happens to the current session state (e.g., whether the loaded map replaces existing content), what 'load into this session' means for subsequent tool calls, or potential failure modes like invalid or expired share ids.

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 efficient sentence plus a concise note about view-link read-only behavior. Every phrase earns its place, and the two clauses complement each other without redundancy. Front-loaded with the primary action verb.

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 single-parameter load tool with no output schema and no annotations, the description covers the core mechanics (what id to provide, edit vs. view semantics) but leaves gaps. It doesn't clarify session state changes, return behavior, or error handling for invalid ids. Given it's a simple tool, this is adequate but not complete — the absence of an output schema and annotations raises the description's responsibility.

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 coverage is 100%, with the id parameter described as 'editId or viewId from a share URL (?id=…)' — already fairly informative. The description adds the semantic distinction that edit ids allow editing while view ids are read-only, which enhances understanding beyond the raw schema. This crosses beyond baseline but doesn't add format or parsing details beyond what the schema provides.

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+resource: 'Load a cloud map by edit or view id into this session.' It clearly identifies what the tool does (loads a shared map) and adds the scope distinction of edit vs. view ids. It doesn't explicitly contrast with siblings, but the edit/view differentiation helps set it apart from roadflow_new or roadflow_get.

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 implies usage context ('Load a cloud map... into this session') and notes that view links are read-only, which gives some when-not guidance. However, it doesn't explicitly state when to prefer this over roadflow_get or roadflow_new, nor does it clarify prerequisites like whether the map must have been shared via roadflow_create_shared first.

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