get_cli_template_group

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

No annotations are provided, so the description carries the full burden. It correctly implies a read-only operation ('Get details') without side effects, but it does not disclose authorization requirements or any potential behavioral nuances. The description is minimal but accurate.

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 extremely concise and front-loaded. It states the purpose in one line, then lists two parameters with brief explanations. Every sentence is essential, and there is no redundant information.

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 simple 'get' operation, the description is complete. It identifies the required parameters and indicates a return value. Since an output schema exists, the description need not detail return fields. The tool's complexity is low, and the description covers all necessary information.

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?

The schema coverage is 0%, meaning the description must compensate. It adds semantic meaning by labeling the parameters as 'ADOM name' and 'CLI template group name', which clarifies their purpose beyond the schema's bare type definitions. However, it does not elaborate on expected formats or constraints.

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 purpose: 'Get details of a CLI template group.' It uses a specific verb 'get' and resource 'CLI template group', and it distinguishes from sibling tools like create_cli_template_group, delete_cli_template_group, and list_cli_template_groups by its focus on fetching details of a single group.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. While the purpose is clear, there is no context about when to prefer this over list_cli_template_groups or other tools. The usage is implied but not explicitly guided.

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