nexo_personal_script_remove

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

No annotations are provided, so the description must cover behavioral traits. It reveals that the tool removes from registry and optionally deletes the file after unscheduling. However, it does not disclose side effects (e.g., irreversible removal), required permissions, or what happens to associated schedules. The transparency is moderate.

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 efficiently conveys purpose and optional behavior. It is front-loaded with the core action and adds no fluff. Every part earns its place.

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's simplicity (2 params, no output schema, no annotations), the description covers the essential purpose but lacks details on return values, error conditions, or prerequisites. It is minimally complete for an agent to understand the function, but not exhaustive.

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 input schema has 0% documentation coverage, so the description adds meaning. It explains that 'name' identifies the script and 'keep_file' controls deletion. The default behavior (delete file) is clarified. However, it does not elaborate on the file's location or format, leaving some ambiguity. Adequate but minimal.

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: remove a personal script from the registry, with an optional file deletion. The verb 'remove' and resource 'personal script' are specific. It effectively distinguishes from the sibling tool 'nexo_personal_script_unschedule' by indicating that this tool goes beyond unscheduling to remove the registry entry.

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 does not explicitly state when to use this tool versus alternatives like 'nexo_personal_script_unschedule' or 'nexo_personal_script_create'. It implies use for removal after unscheduling, but no direct guidance on prerequisites or comparisons is provided.

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