sc_load

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

No annotations are available, so the description carries full responsibility for behavioral disclosure. It only says 'Apply saved configurations', implying a mutating action, but doesn't disclose side effects, whether it overwrites existing configs, or what system state changes. This is minimal transparency.

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 very short, a fragment of two phrases. It avoids verbosity, but it is under-specified rather than efficiently concise. The brevity leaves key details unresolved, so it doesn't earn its place as fully helpful.

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?

With 4 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain what 'configurations' are, how they are loaded, or how flags and persona affect behavior. A single-line description is insufficient for a tool of this 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 description coverage is 100%, with each parameter (args, flags, persona, evidence) having a description. The tool description adds no additional parameter semantics, so it relies on the schema. Baseline 3 applies.

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 'Load configurations - Apply saved configurations' indicates the tool loads/applies saved configs, and the verb 'load' aligns with the tool name. However, it is vague about what configurations are, the context, and how it differs from sibling tools like sc_persona or sc_build.

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 usage guidance is provided. The description does not state when to use this tool, mention prerequisites, or reference alternative sibling tools. Agents have no help deciding between sc_load and other tools.

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