Get All Users

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

Annotations already declare readOnlyHint=true, and the description simply says 'Get information,' which is consistent but adds no behavioral context beyond the annotation. It does not disclose pagination details, response format, or any side effects, though the schema does include a note about per_page affecting paging.

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, efficient sentence that is front-loaded with the key action and resource. It avoids unnecessary detail, though it could have been slightly more specific without losing conciseness.

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?

Given that the tool is relatively simple with only two optional parameters, a good schema, and an output schema present, the minimal description is barely adequate. However, it lacks any mention of paging behavior or how this tool relates to sibling tools, making it less complete for an agent navigating a large toolset.

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 both parameters (page, per_page) are already well-documented in the schema. The description itself adds no parameter-specific information, 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?

The description 'Get information about user accounts registered in the organization' clearly identifies the action (get) and resource (user accounts), and the plural form plus the name 'users_get_all' signal a list operation. However, it doesn't explicitly say 'all' or distinguish it from 'users_search' or 'user_get' in the description text, so it's not a perfect 5.

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 vs alternatives like users_search or user_get. The description does not mention any exclusions or alternative conditions, leaving the agent to infer usage solely from the tool name.

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