list_users

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

The description only adds the HTTP endpoint and repeats 'Get api users'; it does not disclose behaviors beyond the strong annotations. It offers no information about response shape, pagination, or authorization requirements beyond what the output schema and annotations already provide.

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-loaded: 'Get api users.' followed by the endpoint. There is no redundant wording, and the content is appropriately minimal for a zero-parameter read operation.

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 zero-parameter read with a rich output schema and comprehensive annotations, the description is largely sufficient. The only notable gap is not explicitly stating that this returns all users rather than online-only users.

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?

There are no parameters, so parameter documentation is unnecessary. The description does not need to compensate for missing schema meaning, and the schema coverage is effectively complete.

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 clear verb and resource: 'Get api users', and provides the endpoint. This makes the tool's purpose understandable, though it does not explicitly distinguish it from siblings like list_users_online or get_users_by_id.

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 given about when to use this tool versus alternatives. The purpose is implied by the name and endpoint, but there is no mention of exclusions, such as using list_users_online for online users or get_users_by_id for a single user.

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