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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds valuable context about the 'subscription-gated' access requirement, which is an auth-related trait not captured in annotations. This extra context goes beyond what annotations provide, warranting a 4.

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 a single, compact sentence that front-loads the key access constraint ('Subscription-gated') and enumerates the catalog's contents. Every phrase carries meaning, with no redundant or filler text. This is an ideal length for a no-parameter tool.

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?

Given there are no parameters, rich annotations (read-only, open world, idempotent), an output schema, and a clear description of contents, the tool is fully specified. The description covers the essential aspects (catalog contents, access restriction) without needing to explain parameters or return values. It is complete for its scope.

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 has zero parameters, so the baseline is 4 per the rubric. The description adds context about the contents of the catalog (semantic models, intents, evidence requirements, freshness policies), which helps interpret the output. Since there are no parameters to explain, the description need not compensate further.

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 clearly identifies the tool as a catalog of governed semantic models, intents, evidence requirements, and freshness policies. This specific scope differentiates it from sibling tools like atlas7_field_catalog, which focuses on fields. Though it lacks an explicit verb, the noun phrase 'catalog' implies a listing operation, and the resource is precisely defined.

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 implies usage context—if you need model catalog information, this is the tool—but it does not explicitly state when to use it over alternatives or provide exclusions. No alternative tools are named, and the 'subscription-gated' note only hints at access restrictions, not selection criteria.

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