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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful non-obvious context: it returns paginated results and requires a Proof account with an authenticated client, plus the counterintuitive caveat that start_login does not authenticate this tool. That caveat is real behavioral value beyond the schema.

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?

Front-loads the purpose in one sentence, then the pagination note, then the access requirement. No filler, though the auth block is verbose relative to the short core description.

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 read-only, zero-required-param list tool with full schema coverage and no output schema, this is nearly complete: purpose, pagination, and a critical auth caveat are all present. Missing only routing against sibling list/get tools and any indication of what a HITL config contains.

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 each parameter (page, limit, status, environment) is documented with enums and bounds, so the schema carries the burden. The description only says 'optional filters' generically and adds no syntax, defaults, or interaction detail beyond that.

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?

States a specific verb (List) and resource (HITL configs) with scope qualifiers (optional filters, paginated results). The plural/list framing implicitly distinguishes it from get_hitl, but no sibling is named explicitly, so it stops short of a 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?

Gives clear context for use: optional filters, paginated, and a concrete access prerequisite with an explicit exclusion ('start_login does NOT open this tool'). It does not, however, describe when to prefer this over related tools like get_hitl or how the filters interact.

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