nxc_raw

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

No annotations are provided, so the description carries full burden. It implies full control over arguments but does not disclose potential destructive behavior, side effects, or safety risks. The agent is left unaware of the implications of executing arbitrary NetExec commands.

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?

Two concise sentences: the first defines the purpose, the second provides usage guidance. No redundant or extraneous information. Every sentence 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?

The description covers purpose and usage but lacks details on return values, potential side effects, or prerequisites. Given the tool's raw execution nature and lack of output schema/annotations, more context would be beneficial.

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% as the single parameter is described. The description adds 'full control over all arguments' but this is a general statement, not specific to the parameter. It does not provide additional meaning beyond the schema description.

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 'Execute a raw NetExec command with full control over all arguments', specifying the verb 'Execute' and the resource 'NetExec command'. It also distinguishes from sibling tools by stating 'Use for advanced scenarios not covered by other tools.'

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 explicitly says to use this tool for advanced scenarios not covered by other tools, implying when to use. It does not provide explicit exclusions or list alternative tools, but the contrast is clear given the list of specialized sibling tools.

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