list_verified_users

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

No annotations are present, so the description carries the behavioral disclosure burden. It explains the grouping behavior and the unusual authentication requirement that start_login does not enable access. It does not describe pagination details or output shape, but for a simple read-style listing tool this is reasonable coverage.

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 purpose is front-loaded in a single sentence, and the access note is short but valuable. There is slight redundancy between 'grouped by external_user_id' and 'Shows all verifications per user,' but overall the description is efficient and free of filler.

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 tool with only two optional pagination parameters and no annotations, the description adequately covers what the tool does and the critical setup prerequisite. It would benefit from a brief note on return format, but that is not essential given the simple list semantics.

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?

The input schema already fully describes page and limit, including types, constraints, and descriptions, with 100% schema description coverage. The tool description adds no additional parameter meaning, so the baseline score of 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?

The description states a specific verb and resource: 'List verified users grouped by external_user_id.' It also clarifies that it shows all verifications per user, which distinguishes it from flat verification listers like list_verifications and from single-user getters like get_verified_user.

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 description gives clear access context: a Proof account is required, PROOF_API_KEY must be set, the server must be restarted, and start_login does not open this tool. It does not explicitly compare against alternative tools, but the access guidance is concrete and actionable.

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