dcs_security_group

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

Annotations already declare readOnlyHint=true, and the '[READ]' prefix merely restates that. The description adds nothing beyond the annotation: no behavior for an unknown group_id (empty vs error), no permission requirements, and no return shape, even though no output schema exists.

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?

Six words, front-loaded with a read marker and the core action. Nothing is wasted, though the brevity reflects under-specification rather than disciplined economy.

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 single-record lookup with an undocumented required ID parameter and no output schema, the description should say something about the identifier's origin and what is returned. Neither is present, leaving the agent with only the tool name to infer behavior.

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 has one parameter (group_id) with 0% description coverage, and the description does not compensate at all — it never mentions the parameter, its type, or how to obtain a valid ID. The agent gets no meaning beyond the property 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 name plus description state a specific verb and resource ('Read one security group'), and 'one' weakly implies a single-record fetch. However, it never explicitly contrasts with the sibling dcs_security_groups (plural listing) or dcs_security_group_stats, so the agent must infer the singular/plural distinction from naming alone.

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 guidance on when to use this versus dcs_security_groups or dcs_security_group_stats. No prerequisites, no mention of where a group_id comes from, and no exclusions are stated.

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