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

With no annotations provided, the description carries the behavioral disclosure burden. It does add one meaningful behavior: 'View links are read-only.' However, it does not clarify whether edit ids allow modifications, what the tool returns, or any auth/error 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?

Two short sentences with no filler. The main action and resource are front-loaded, and the only additional sentence adds a meaningful constraint. Every word earns its place.

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?

This is a simple one-parameter tool with 100% schema coverage, so the missing output schema is not a major problem. The description covers the operation, the id source, and a key behavioral distinction. It could be slightly more complete with explicit sibling differentiation, but it is sufficient for reliable invocation.

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 input schema already documents the 'id' parameter well, so the baseline is 3. The description adds value by tying parameter choice to behavior: passing a view id results in a read-only graph. This is actionable semantic information beyond the schema's format-only description.

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, 'Load', a specific resource, 'cloud Artifacts graph', and the lookup mechanism ('by edit or view id'). This clearly distinguishes it from create/export/discard siblings. However, it does not explicitly differentiate it from the closely related artifacts_get or roadflow_open_shared tools.

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 when to use this tool: when you have a shared Artifacts edit or view id. The phrase 'View links are read-only' gives a practical usage constraint. But it does not explicitly state when to prefer this tool over alternatives such as artifacts_get or roadflow_open_shared.

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