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

The annotations already mark the operation read-only and non-destructive; the description adds an auth dependency by requiring a prior NPKI session login with a matching account_link_id. It does not describe return format, pagination, or error behavior, so its behavioral disclosure remains useful but limited.

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?

Two short sentences, with the critical prerequisite front-loaded in uppercase and the operation stated plainly. There is no filler or repetition.

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 search with fully documented parameters and a known prerequisite, the description is nearly complete. The only minor gap is not explicitly noting that this returns a list-level result and that the detail siblings target individual notices, but an agent can invoke the tool correctly from the existing information.

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 describes all four parameters, including the optionality and auto-resolution behavior of account_link_id, at 100% coverage. The description adds no parameter-level details, so the schema carries the full burden and the baseline of 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?

The description names a concrete action and resource: 'Search COMWEL premium billing notices,' which clearly identifies this as a list/search operation. It does not explicitly distinguish itself from the sibling premium_billing_notice__detail or individual_billed_premium__detail tools, 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?

The opening sentence gives an explicit precondition: a prior comwel__auth__npki_session__login with the same account_link_id. That tells the agent when in the workflow it may be invoked, but it does not discuss when to prefer this search over the sibling detail tools or any exclusions.

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