ad_get_privileged_users

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

With no annotations provided, the description carries the full behavioral burden, and the only hints are the bracketed tags [Security & Audit] [READ]. It does not state which groups count as privileged, whether it scans nested group membership, or whether elevated permissions are needed. For a security-audit read with zero annotation coverage this is thin.

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 sentence is short, front-loaded with categorization tags, and contains no filler. It is under-specified rather than bloated, which is a different defect.

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 covers return values, so that need not be explained. However, for a security-sensitive enumeration tool with no annotations and no parameter documentation, the definition omits the scope of "privileged" entirely — the single most important thing for calling it correctly.

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 optional correlation_id parameter, and the description offers no compensating explanation of its role (presumably request tracing) or of the fact that it can be omitted. The schema alone leaves it ambiguous to a naive caller.

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 names a verb ("Identificar") and a resource ("usuarios em grupos privilegiados"), so the intent is graspable, but "privileged groups" is left undefined and there is no differentiation from closely related siblings like ad_get_domain_admins, ad_get_admin_count_users, or ad_list_group_members. An agent cannot tell from the description alone which of these to call.

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 prerequisites, and no mention of alternatives. The sibling list contains at least three overlapping admin/privilege tools, and the description gives no routing signal between them.

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