dcs_security_group_stats

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

readOnlyHint=true already declares the safety profile, and '[READ]' merely repeats it. Beyond that, the description says nothing about what the counts represent — total groups only, counts per policy, per tag, or per role — nor anything about auth requirements or result shape, which is exactly the context a count endpoint needs.

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 front-loaded sentence with no filler. The '[READ]' prefix is redundant with the readOnlyHint annotation but costs little, and the statement is not padded with vague boilerplate.

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?

With no output schema and no parameters, the description carries almost the entire burden, yet it never explains what the returned counts are keyed by. The tool is simple enough that an agent can invoke it blindly, but it cannot predict the response structure from this text.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is trivially complete.

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?

States a specific verb ('Read') and resource ('security group counts'), which distinguishes it in intent from the sibling list/entity tools dcs_security_groups and dcs_security_group. However, it never names those siblings or explicitly contrasts itself, so the differentiation must be inferred from the word 'counts'.

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 call this versus dcs_security_groups (list) or dcs_security_group (single entity), and no stated preconditions. The agent must guess that this is the lightweight aggregated-count endpoint.

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