remote_command_groups

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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which alone would leave it unclear why a 'list' tool is not read-only. The description fills that exact gap by explaining that the optional flags create a persistent local plug-in directory and reload modules, and the 'once' wording reinforces idempotency. It stops short of saying where the directory lives or what permissions are needed.

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?

Three short sentences with no filler, and the per-flag instructions are split cleanly. The opening sentence is slightly ambiguous in pairing 'list command groups' with 'and the persistent local plug-in directory,' which makes the object of the listing unclear.

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?

An output schema exists, so return values need not be described. However, the central concept, the persistent local plug-in directory, is left unexplained (no location or scope), and the relationship between listing command groups and toggling these flags is not fully coherent for an agent deciding how to call it.

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?

With schema description coverage at 0%, both parameters would otherwise be bare booleans with defaults. The description gives each one operational meaning (create_directory creates the plug-in folder; reload refreshes after module edits), which meaningfully compensates. It does not explain what 'reload' actually reloads or the consequence of leaving it false, leaving a small residual gap.

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 names a specific verb and resource: listing command groups plus the persistent local plug-in directory. It is clear enough to distinguish this listing/inspection tool from siblings such as remote_command_group_run or remote_execute, though it never explicitly contrasts itself with the closely related remote_command_group_describe.

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?

Usage is stated only for the two flags: create_directory=true 'once' to create the folder, and reload=true 'after adding or editing a module.' There is no guidance on when to call this tool instead of remote_command_group_describe or the other command/group tools, so the agent must infer the routing.

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