sgraph_load_model

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the tool returns an ID and is idempotent when the model was auto-loaded at startup, but it does not state whether a load overwrites existing state, whether the operation is mutating, or what error conditions can occur.

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 concise sentences front-load the core action and output, then cover the conditional auto-loaded behavior. There is no filler, repetition of schema fields, or unnecessary detail.

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 one-parameter tool with no output schema, the description captures the essential call contract: provide a file path, receive an ID, and handle the already-loaded case. It omits file-format and error-behavior details, but the core usage context is sufficiently complete for a tool of this low complexity.

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 0%, so the description must compensate for the single 'path' parameter. 'Load ... from file' clarifies that the path identifies a file location, but it adds nothing about accepted file formats, path resolution, or restrictions. This is minimal but adequate for a single self-descriptive parameter.

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 names a specific verb ('load'), a precise resource ('graph model'), and the source ('from file'), and it states the output (an ID for subsequent queries). It is clearly distinct from its siblings, which all query or analyze an already-loaded model.

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 phrase 'for subsequent queries' frames the tool as the entry point before using other graph operations, and the auto-loaded note tells agents when calling it may be a no-op. It does not explicitly list exclusions or alternatives, but no sibling performs loading, so there is no competing tool to rule out.

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