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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real context: an administrator-authority requirement, a data-scope caveat ('does not list secrets'), and a result-interpretation caveat ('does not imply verified connector availability') — useful behavioral framing beyond the structured hints.

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 tight sentences, front-loaded with the operation and scoped by the two caveats. No filler and nothing restated from the name or schema.

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?

With an output schema present, return values need not be explained, and the description covers auth requirements and result caveats. It leaves pagination/ordering semantics to the schema and offers no sibling routing, so it is strong but not fully 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%, with q, limit and cursor each fully documented in the schema, so the baseline is 3. The description adds nothing about parameter syntax, filtering behavior, or cursor semantics beyond what the schema already states.

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 ('Page') and resource ('independent configured account roots') plus the authority context ('current administrator authority'). It does not explicitly name a sibling such as connections.list or connections.catalog to disambiguate, so it falls 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 description never says when to choose this over siblings like connections.list or connections.catalog, nor does it state any exclusion or precondition beyond 'administrator authority'. Usage is only faintly implied by the resource being paged.

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