remote_command_groups

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

No annotations are provided, so the description must disclose side effects. It states that create_directory creates a folder (one-time) and reload is needed after module edits, implying state changes. However, it does not detail what happens if the folder already exists, whether reload re-scans, or any permission requirements.

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 two sentences, front-loaded with the primary purpose, followed by concise parameter guidance. Every sentence earns its place with no repetition or filler.

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?

For a tool with two optional boolean parameters and an output schema, the description covers the essential usage. It mentions the persistent local directory and flag conditions. It is sufficient, though it could note that the primary action is a list operation with optional side effects.

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 0%, so the description must explain the parameters. It does so effectively: create_directory=true creates the folder, reload=true refreshes after edits. This adds meaningful semantic context beyond the bare boolean schema.

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's function: 'List command groups and the persistent local plug-in directory.' This is a specific verb+resource combination that distinguishes it from siblings like remote_command_group_describe and remote_command_group_run.

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 explicit usage instructions for the optional flags: 'Set create_directory=true once to create the folder. Set reload=true after adding or editing a module.' This clarifies when to use the tool and when to set each flag, though it does not contrast with sibling tools.

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