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

No annotations are provided, so the description carries the full burden. It discloses return content ('allowlist identifiers and total_count'), a prerequisite, and the cost in tokens. It does not explicitly state read-only safety, but 'List' implies it, and the added context about connections and cost goes beyond the obvious.

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 four concise sentences, each adding distinct value: purpose, prerequisite, parameter targeting, and return content. It is front-loaded with the core purpose and avoids redundancy.

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 list tool with no annotations and an output schema, the description covers the key contextual elements: prerequisite, targeting, return shape, and cost. It could mention pagination behavior explicitly, but the schema covers limit/offset, so the description is sufficiently 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 baseline is 3. The description reinforces the clerk_instance_id parameter's meaning ('Pass clerk_instance_id to target a specific connection, or omit it to use the default account') but adds little beyond the schema. No additional semantics for limit and offset are provided.

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 uses a specific verb ('List') and identifies the resource ('allowlisted identifiers') with a clear scope ('in a connected Clerk instance'). It distinguishes itself from sibling tools like create_allowlist_identifier and list_blocklist_identifiers by clearly stating it lists allowlist identifiers.

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 provides a clear prerequisite ('Call clerk.get_connected_accounts first') and explains how to target a specific connection versus using the default. It does not explicitly mention when to use this over alternatives, but the context is sufficient for a list operation.

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