List users crews

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is lower, and the description still adds real value: the underlying endpoint, the disclosure that it was inferred from the web app's own traffic, and an explicit instruction to confirm results. That reliability warning is exactly the kind of behavioral context annotations cannot convey; only the pagination/volume behavior is left unstated.

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?

Information is front-loaded in a logical order: purpose, endpoint, reliability caveat, query params, return shape. The first sentence duplicates the title verbatim and could be replaced with a substantive scope statement, but the long field list earns its space given there is no output schema.

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, enumerating the returned keys (id, name, email, role_id, route_capacity, etc.) is genuinely useful and fills that gap. The remaining hole is the core ambiguity of users vs. crews and what the two entity types mean here, which the field list alone does not resolve.

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% and there are only three parameters, so the schema carries the load. The description names addUnassignedUser as a query param seen in traffic, which confirms it is real, but it never explains what the flag does or how extra_query interacts with it.

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 opening sentence "List users crews" restates the title and leaves it ambiguous whether this returns users, crews, or a combined roster. The GET path and the note that it was inferred from observed web traffic add some specificity, but nothing distinguishes it from sibling singleops_read_list_users_current, which an agent would plausibly confuse it with.

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 statement of when to call this versus singleops_read_list_users_current or singleops_read_search_labor_resources, and no prerequisites or exclusions. The "confirm results" caveat is a reliability note, not usage guidance, so the agent must infer selection 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.