get_users

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the scope ('on the InvoiceShelf instance') but does not disclose pagination behavior, default limits, or whether the response is a paginated list. With annotations covering the safety profile, a 3 is appropriate.

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?

A single sentence that is front-loaded with the verb and resource. No wasted words, and the scope is stated efficiently.

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 simple list tool with readOnlyHint=true and two self-explanatory parameters, the description is mostly adequate. However, it does not mention pagination behavior or response format, and with no output schema, an agent might not know what to expect. The lack of usage guidance relative to get_user is a minor gap.

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 0%, so the description carries the burden for parameter meaning. The description does not explain 'page' or 'limit' beyond their names, which are fairly self-explanatory for a list operation. It adds no detail about defaults, maximum values, or pagination format, so it only partially compensates for the schema gap.

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 states a specific verb ('List') and resource ('users on the InvoiceShelf instance'), clearly distinguishing it from sibling tools like get_user (singular) and get_customers (different resource). It lacks explicit differentiation from get_user, but the plural form and instance scope make the purpose clear.

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?

The description implies a list operation with no filtering details, and the sibling set includes get_user for singular retrieval. However, it does not explicitly state when to use this tool versus get_user or how pagination should be handled. The context is clear enough for a basic list call but lacks explicit routing guidance.

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