nexo_personal_script_create

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

With no annotations, the description must disclose behavioral traits. It states creation, registration, and optional schedule attachment, but does not mention what happens on duplicate names, whether overwrites occur, required permissions, or side effects like file system changes beyond the stated path.

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?

Single sentence, no redundant words. Information is front-loaded and clear.

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 creation tool with 5 parameters and no output schema, the description is too brief. It lacks information on return values, error handling, prerequisites (e.g., does the directory need to exist?), and the exact behavior of registration. Not complete enough for reliable use.

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 description must add meaning. It explains that 'schedule' and 'interval_seconds' relate to optional schedule attachment, but does not detail the meaning of 'name' (likely the script filename), 'description', or 'runtime' options. Partial value added but insufficient compensation.

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?

Description clearly states the tool creates a new personal script, registers it, and optionally attaches a schedule. The verb 'create' and resource 'personal script' are specific, and the location (NEXO_HOME/personal/scripts) is given. This distinguishes it from sibling tools like list or remove.

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 guidance on when to use this tool versus alternatives like nexo_personal_plugin_create or other script management tools. There is no mention of prerequisites, context, or exclusion criteria.

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