dcs_users

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

Annotations already declare readOnlyHint=true, so "[READ]" adds no information. The description discloses nothing beyond that: no indication of result volume, whether the list is paginated or truncated at the limit, or what a "management user" record contains. With annotation coverage this sparse, the description should carry more of the burden than it does.

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?

Four words, front-loaded and free of filler, so nothing is wasteful. But this level of terseness reads as under-specification rather than efficient writing — there is room to add scoping and return-shape detail without bloat.

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 list endpoint with no output schema and an undocumented `limit` parameter, the description should say what comes back and how paging behaves. Neither is present, so an agent knows the tool returns users but not how much of the user set or in what form.

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%, so the single optional `limit` parameter is documented nowhere — its default of 100 is only visible as a schema default, with no statement of maximums, paging semantics, or whether omitted means all users. The description does not compensate for this gap at all.

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 verb and resource ("List management users"), which at least tells an agent this returns user records rather than policies or alerts. However, "management users" is undefined — it doesn't clarify whether these are admin/console users, licensed users, or directory accounts, and among ~35 sibling tools there is no differentiation beyond the noun "users".

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 only guidance is the "[READ]" tag, which merely restates the readOnlyHint annotation. There is no when-to-use context, no mention of related siblings such as dcs_roles or dcs_role_users, and no exclusions, so the agent must infer placement from the tool list alone.

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