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

With no annotations, the description carries the burden. It discloses what is returned (readiness, catalog set, host identity) but not whether it is read-only, requires auth, or mutates state. The token parameter implies an access-control dimension that the description never addresses.

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?

It is a single sentence, but it packs three disparate concerns (readiness, catalog set, host identity) behind a colon-led list that is hard to parse and not front-loaded on the primary purpose.

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?

An output schema exists, so return values need not be explained, and parameter count is minimal. However, with no annotations and a broad sibling set, the description leaves auth requirements and usage context unaddressed.

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 coverage is 100%, so the schema already fully documents the single token parameter. The description adds no parameter detail, so baseline 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 name 'status' is generic, but the description does enumerate three concrete outputs: readiness, the aggregate catalog set, and host identity (origin and originAliases). It is specific about resource content but does not distinguish itself from siblings like ui_builder_list_catalogs, which also relates to catalogs.

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?

No guidance on when to call this versus alternatives, despite a large sibling set containing catalog-listing and access tools. The only usage-adjacent hint is embedded in the token parameter, not the description body.

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