system

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

With no annotations, the description should disclose behavioral traits. It mentions actions like 'shell: run command' and 'permission_*' but does not warn about side effects, required permissions, platform restrictions, or potential destructive behavior. The terse descriptions are insufficient for informed invocation.

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 concise but unevenly structured; it uses a list format that front-loads categories, but the information is fragmented and lacks a clear hierarchical structure. Every sentence adds some value, but clarity could be improved.

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 complexity (14 parameters, 20+ actions) and no output schema, the description is too brief. It fails to explain how actions relate to parameters, expected outcomes, or platform-specific behaviors. The description is incomplete for the tool's scope.

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 93%, so the schema already documents most parameters. The description adds minimal value by grouping parameters under action names but does not explain parameter interactions or provide examples. Baseline 3 is appropriate.

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 lists the tool's subcategories (shell, logs, clipboard, permissions, files) and implies it handles system-level operations, differentiating it from siblings like app or device. However, the overall purpose is not explicitly stated as a single verb+resource.

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 provides no guidance on when to use this tool versus the sibling tools. It simply lists available actions without context for selection, leaving the agent without decision support.

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