mcp-ninjaone

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the script must exist, which is a useful constraint, but fails to cover critical aspects: it doesn't indicate whether this is a read-only or destructive operation (execution could modify device state), doesn't specify authentication needs, rate limits, or potential side effects (e.g., device reboots, job queuing). For a tool that executes scripts, this lack of behavioral context 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 a single, efficient sentence that front-loads the core action ('Execute a saved script on a specific device') and adds a necessary constraint ('The script must already exist...'). There is zero waste or redundancy, making it highly concise and well-structured for quick understanding.

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 complexity of executing scripts on devices (a potentially destructive operation), no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., safety, permissions), output format (e.g., job ID, success/failure), and error handling. For a tool with 4 parameters and significant implications, this minimal description fails to provide adequate context for safe and effective 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?

The schema description coverage is 100%, meaning all parameters are documented in the input schema (e.g., device_id, script_id, run_as with enum values, parameters). The description adds no additional parameter semantics beyond what's in the schema, such as explaining script library access or parameter formatting. Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('Execute') and target ('a saved script on a specific device'), with the constraint that the script must exist in NinjaOne's library. It distinguishes from sibling tools like 'get_device' or 'list_running_jobs' by focusing on script execution rather than data retrieval or job management. However, it doesn't explicitly differentiate from potential similar tools like 'run_script' if they existed, keeping it at 4 instead of 5.

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 by stating the script must already exist, which provides some context for when to use it (i.e., after script creation). However, it lacks explicit guidance on when to choose this tool over alternatives (e.g., vs. running scripts on multiple devices or using different execution methods), and doesn't mention prerequisites like device connectivity or permissions. This leaves usage somewhat inferred rather than clearly defined.

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