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

Annotations already declare read-only, non-destructive, open-world behavior, so safety is covered. The description adds meaningful context beyond that: it returns personal data, and it discloses the underlying endpoints (GET /users/all/ or /users/filtered/) and paging shape. It omits rate limits or permission requirements, keeping it from a 5.

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 two short sentences with the core purpose front-loaded, followed by a PII warning and endpoint detail. The endpoint parenthetical is slightly opaque but not wasteful; nothing needs to be cut.

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 no output schema, the description says it returns the fields requested and warns of personal data, which is enough to call it correctly. The only real gap is that it does not clarify its relationship to axislms_list_users, but for a three-parameter search tool the invocation context is otherwise complete.

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 the schema already fully documents page, fields, and user_filter syntax. The description adds only a concrete filter example and a loosely worded field-selection note, duplicating rather than extending the schema's detail; baseline 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?

It states a specific verb+resource ('Page through all users' / search with a phrase) and adds field-selection and paging scope, so an agent can tell it is a filtered user listing with chosen fields. It stops short of naming sibling tools; distinction from axislms_list_users and axislms_get_user is left implicit.

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 two modes (all users vs filtered users) imply when the tool is useful, and the example phrase shows the filter form. However, it never states when to prefer this over axislms_list_users or axislms_get_user, nor any when-not condition.

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