Get Users

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

Annotations provide no safety hints (e.g., readOnlyHint), so the description carries full burden. It only states a simple fetch operation, without disclosing pagination, rate limits, or that the keyword parameter is required but nullable to return all users. This lacks the behavioral context needed for safe 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 description is a single, front-loaded sentence that uses no filler words. It efficiently conveys the core purpose without unnecessary detail, making it easy to parse.

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 an output schema and detailed parameter schema, the description is minimally sufficient for a simple list tool. However, the required-but-nullable keyword parameter and absence of usage context around filtering could confuse an agent, leaving room for improvement in guiding full invocation.

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?

The schema description covers 100% of the parameter, detailing that keyword performs case-insensitive partial matches on id, name, displayName, or email. The tool description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 clearly states the tool fetches all users in the Linear organization with a specific verb ('Fetches') and resource ('users'). This immediately distinguishes it from sibling tools like get_issue and get_projects, which target different entity types.

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, nor any exclusions or prerequisites. The description does not mention whether a keyword is needed or how to fetch all users without filtering, leaving the agent to infer usage from the schema.

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