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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the endpoint and the shape of the returned objects, but says nothing about page-size ceilings, result ordering, or how next_page tokenization behaves beyond what the schema's next_page hint already implies.

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 front-loaded sentence with the resource first and the endpoint last; nothing is wasted. It is arguably a touch terse for an agent that must pick between it and list_people, but structurally sound.

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?

No output schema exists, so enumerating the returned fields is the right compensating move, and pagination semantics are fully handled by the schema. The only real gap is the missing disambiguation from intellihr_list_people.

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 both parameters (page, limit) carry full descriptions including defaults and the 'pass the previous reply's next_page' instruction. The description adds no parameter meaning of its own, so the baseline 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?

Names the concrete resource ('user accounts that can sign in to intelliHR') and enumerates the returned fields (username, enabled flag, permission groups, linked person), plus the underlying endpoint GET /users. It implicitly separates itself from intellihr_list_people by scoping to sign-in accounts, but never says so outright.

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 'accounts that can sign in' framing implies the use case (auth/permission administration), but there is no explicit when-to-use or when-not-to-use statement, and no pointer to intellihr_list_people for the human-record case, which is the most likely sibling confusion.

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