Get Users

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the word "page", which is already implied by the page/pageSize parameters, and says nothing about result volume, default ordering behavior, or permission scoping.

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?

It is short, but the first line "Get Users." merely duplicates the title verbatim and earns nothing. The single substantive sentence is front-loaded and free of noise, but the definition is under-specified rather than genuinely concise.

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 six-parameter list tool, the description contributes no context beyond the resource name. An agent cannot learn from it what a returned user contains, whether pagination metadata is returned (no output schema exists to compensate), or how this differs from the single-user siblings.

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 every parameter — including the non-obvious roleFilter min/equals/max hierarchy semantics and case-sensitivity of sortBy — is documented in the schema itself. The description adds no additional parameter meaning, so the baseline of 3 applies.

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?

"Retrieves a page of users" restates the tool name and title ("Get Users") with no additional specificity. It conveys the resource and that results are paginated, but gives an agent nothing to distinguish it from the many siblings that also return user-shaped data, such as get_user, get_user_by_email, or list_contacts.

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 when-to-use guidance at all: no mention of when to call this versus get_user or get_user_by_email when a specific person is known, and no mention of when the role/sort filters are appropriate. Usage must be inferred entirely from the schema.

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