remote_command_group_describe

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data rather than the description. The description adds nothing beyond that: it does not say whether an unknown group errors, whether the result is static metadata, or how large the output is, and the output schema covers the return shape.

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?

A single tight sentence with the purpose front-loaded and no filler. It is efficient, though the brevity comes at the cost of the missing details noted above.

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 output schema relieves the description of explaining return values, but for a required-identifier introspection tool the description should at least say how to obtain a group name and what an invalid group does. With 0% schema coverage on the only parameter, neither the schema nor the description closes that gap.

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 description coverage is 0% for the single required 'group' parameter, and the description offers no compensating meaning — it does not say whether 'group' is a name, slug, or ID, or where a valid value comes from. The word 'group' is merely echoed from the parameter name.

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 verb 'describe' and the resource 'command group' are stated, and 'actions and parameters' hints at an introspection tool. However, 'specialized command group' is never defined, and nothing distinguishes this from the sibling remote_command_groups (which presumably enumerates groups) or remote_command_group_run (which executes one).

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?

There is no when-to-use guidance, no mention of calling remote_command_groups first to discover a valid group name, and no statement that remote_command_group_run is the follow-up action. An agent must infer the entire workflow from tool names.

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