NEXO Brain

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

No annotations are provided, so the description carries full burden. It states the tool loads/reloads plugins but doesn't disclose critical behavioral traits: whether this is a safe operation, what happens if the plugin fails to load, if it requires specific permissions, if changes are immediate, or what the output contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args section is clear but could be integrated more seamlessly. There's minimal waste, though it could be slightly more structured for optimal readability.

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?

Given the tool has an output schema (which reduces need to describe return values) but no annotations and low schema coverage, the description is moderately complete. It covers the basic action and parameter but lacks behavioral context, error handling, and differentiation from siblings. For a plugin management tool with mutation implications, it should provide more operational guidance.

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 0%, so the description must compensate. It adds the parameter 'filename' with an example ('entities.py'), clarifying it refers to a plugin filename in the plugins directory. However, it doesn't explain format constraints (e.g., file extension requirements), path handling, or if subdirectories are supported. The description provides basic semantics but leaves important details uncovered.

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 or reload') and target resource ('a plugin from the plugins/ directory'), providing specific verb+resource. However, it doesn't explicitly distinguish this tool from sibling tools like 'nexo_plugin_list' or 'nexo_plugin_remove', which would require mentioning it's for dynamic loading/reloading rather than listing or removing plugins.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., plugin file must exist), when reloading is appropriate versus initial loading, or how it differs from sibling plugin tools. There's only basic usage context implied by the filename parameter.

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