motion_users

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'Manage users' misleadingly implies mutating operations, while the schema reveals only read-style operations (list/current). It also does not disclose authentication requirements, side effects, or any limitations.

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 compact and front-loads the resource. However, the vague word 'Manage' earns less than a fully tight description like 'List users or get current user information' would, so it is concise but slightly imprecise.

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 and no annotations, the description leaves important context—operation semantics, filter behavior, and return expectations—unstated. An agent would need to infer most behavior from the input schema alone, making this incomplete for a multi-operation 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 schema already documents all four parameters. The description adds no extra meaning beyond loosely implying the 'current' operation via 'get current user information', which matches the baseline of 3.

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 identifies the resource ('users') and one specific operation ('get current user information'), but the leading verb 'Manage' is vague and overstates the scope—the schema only supports 'list' and 'current', not general user management. It does distinguish the tool from sibling tools by resource, but not by operation.

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 choose 'list' vs 'current', nor any mention of team/workspace filtering or when this tool should be preferred over alternatives. The only implicit usage signal is that it is user-related, which is not enough for correct operation selection.

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