run_background_script

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

Discloses it creates a Fix Script record, runs as admin, and warns about safety. However, lacks detail on execution side effects, output, or error handling. Without annotations, transparency is adequate but not thorough.

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?

Extremely concise with three short sentences, front-loading important info (IMPORTANT), and no superfluous text.

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 no output schema or annotations, the description adequately covers purpose and safety but omits expected output or how to verify execution. Dry run explanation helps, but post-execution behavior is unclear.

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 100%, so description adds limited value beyond schema. It reinforces the dry_run parameter's purpose but does not deepen understanding of name or script parameters.

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 tool executes a server-side script in ServiceNow using the Background Scripts table, with specific verb and resource. It distinguishes from sibling tools that are unrelated.

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?

Provides clear usage guidelines: only use safe, tested scripts and always dry run first. Does not explicitly mention when not to use or alternatives, but context is sufficient for safe usage.

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