asana_get_multiple_users

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Get multiple users' and fails to mention that workspace is required, that pagination is controlled by limit/offset, or any other behavioral traits. This is a complete absence of transparency.

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 description is concise in word count but under-specified. It is a five-word tautology that fails to earn its place; it provides no useful structure or content beyond restating the tool name.

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?

Without an output schema or annotations, and with only a minimal description, this tool is severely underdocumented. The description does not explain what 'multiple users' refers to, the required workspace parameter is unmentioned, and there is no context for pagination or filters. It is inadequate for a 5-parameter tool.

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 baseline is 3. The description adds no parameter semantics, but the schema already documents all five parameters adequately, including types and defaults.

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 'Get multiple users' is essentially a restatement of the tool name 'asana_get_multiple_users'. It provides no differentiation from sibling tools like asana_get_users_in_workspace or asana_get_users_in_team, and lacks any mention of scope (workspace/team).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions, leaving the agent without any basis to choose this over sibling list tools.

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