plugin_load

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic action without mentioning side effects like network requests (installing from NPM), file system access, validation, or whether the operation is reversible. Critical safety information is missing for a tool that loads external code.

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 sentence that conveys the core purpose without any unnecessary words or details. It is highly concise and easy to parse.

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?

Despite having two parameters and no output schema, the description provides no information about what happens after loading (e.g., return value, errors, state changes). For a plugin loader, an agent needs to know if loading is synchronous, if it validates the plugin, or if it returns an identifier. The omission leaves significant gaps.

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 description hints that the 'source' parameter can be an NPM package name or local file path, adding some meaning beyond the schema. However, it completely ignores the 'config' parameter (a nested object), which remains unexplained. With 0% schema coverage, the description should compensate more.

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 clearly states the action (Load), the resource (GovernFlow plugin), and the means (from NPM package name or local file path). It is specific and distinguishes itself from siblings like plugin_unload and plugin_list, which are different operations. There is no ambiguity about what the tool does.

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 when you need to load a plugin, and no sibling tool provides an alternative loading mechanism, so exclusions are not needed. However, it does not explicitly state prerequisites or when not to use it, which prevents a perfect score.

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