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

Annotations already declare this a read-only, idempotent, closed-world listing, so the safety profile is covered. The description adds genuinely non-obvious domain behavior — the four tier vocabularies and their operational meaning (live vs credentials vs bridge vs guided) — plus an explicit constraint on how results may be characterized to users ('do not describe a guided connector as automatic').

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 what the resource is before the tier glossary. The backticked tier vocabulary is dense but each term earns its place since it defines returned semantics; only the slightly awkward '`tier_means` in words' phrasing adds friction.

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?

There is no output schema, so the description carries the burden of explaining returned content — and it does, by defining the `tier` field and its four possible values. What remains uncovered is whether the list is paginated or includes connector metadata beyond tier, a minor gap for a zero-parameter catalog tool.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies an unfiltered full listing and adds nothing misleading about inputs.

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 the concrete resource — external systems Aeroz can connect to — and enumerates the categories (WMS, ERP, commerce, EPCIS), which is enough to know this is the connector catalog. It does not, however, differentiate itself from the near-identical sibling `list_integrations`, leaving an agent to guess which catalog to open.

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?

Usage is only implied: the description explains what tiers mean, which signals 'use this to interpret or explain connector options to a user'. There is no explicit when-to-use statement, no exclusion, and no mention of `list_integrations` as the alternative, so the agent must infer routing.

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