users_get_collection

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no mutation/read semantics beyond the implied GET, no pagination behavior, no rate limits, no authentication requirements, no note on how sort/limit/include interact. A bare endpoint string is insufficient for a 9-parameter operation.

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 single string is short but not concise in the useful sense — it is under-specified and redundant, repeating the path twice in parentheses. Brevity here reflects missing content rather than efficient front-loading.

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 9-parameter, zero-required collection endpoint with no annotations and no output schema, the description supplies neither purpose, usage context, nor response shape. Almost everything an agent needs to invoke this correctly must be inferred from the tool name and schema keys.

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 100%, so the schema itself documents all nine parameters (sort, limit, include, field selections, role/username/app filters) with descriptions and enums. The description adds nothing beyond the schema, but the baseline of 3 applies when the schema does the heavy lifting.

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 only restates the raw HTTP path 'GET /v1/users', which duplicates the tool name and title without saying in plain language what it returns (a paginated list of users). An agent can infer 'list users', but there is no differentiation from close siblings such as users_get_instance, users_visible_apps_get_to_many_relationship, or user_invitations_get_collection.

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 tool versus alternatives, no mention of required privileges or scope, and no indication that this is the collection-level listing operation rather than the single-user retrieve. The agent is left to guess from the name alone.

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