hyprctl_raw

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

No annotations exist, so description carries the full burden. It explains the tool executes raw subcommands and warns about the 'dispatch' syntax change. It does not detail side effects, permissions, or error behavior, but for an escape hatch it provides adequate clarity.

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 sentences cover purpose, usage, examples, and a special note. Every word adds value; no fluff or repetition. Front-loaded with the core purpose.

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 (one param, no output schema), the description is mostly complete. It covers what subcommands to use and how to format arguments. It does not describe return format or error scenarios, but for an escape hatch this is acceptable.

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 covers 100% of parameters (1 param: 'args'). Description adds examples, clarifies that arguments are passed as plain argv to hyprctl, and mentions the syntax nuance for 'dispatch' and JSON output. This adds significant meaning beyond the schema alone.

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 raw hyprctl subcommands not covered by 'dispatch'. It lists examples like 'reload', 'version', 'layers', and distinguishes from sibling tools by specifying it's for commands other than 'dispatch'.

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?

Explicitly excludes 'dispatch' and explains the syntax difference (plain argv vs Lua expressions). Advises passing '-j' for JSON output. Does not explicitly contrast with other sibling tools beyond 'dispatch', but the context of being an 'escape hatch' implies using it only when no specific tool exists.

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