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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the behavioral cost disclosure that `include_coverage` is a heavier read. It also explains the semantics of the returned sets (which rules are actually effective) and glob matching, though it says nothing about ordering or result size limits.

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?

Purpose is front-loaded in the first clause, and the parenthetical breakdowns of `scope` values and flag effects are informative rather than filler. It is a single dense block, however, and the backtick-heavy detail makes it heavier than a list tool strictly needs.

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 no output schema, the description must carry the return-shape burden, and it does: it names the collections to expect and their contents, explains `scope` semantics, glob matching rules, and what the optional coverage block contains. Nothing essential for calling or interpreting this read tool is missing.

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%, and the tool has only 3 optional params, so the baseline is 3. The description's flag explanations largely restate the schema descriptions (account-wide catalogs, coverage match counts) rather than adding new syntax or constraints beyond them.

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 (lists) and resource (import classification rules in scope for a model), then enumerates the three returned collections (`sets`, `mappings`, `templates`) with what each contains. It also distinguishes itself from `layerz_manage_mapping` by naming the import_template op that acts on catalogs, so an agent can separate listing from mutation.

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?

Explains the conditions under which each flag matters (`include_user_mappings: true` widens to account-wide catalogs; `include_coverage: true` adds per-rule counts and a coverage block) and clarifies that a model classifies only with its own `model` rules until a catalog is imported. It doesn't explicitly state when-not-to-use or name a read alternative like `layerz_list_templates`, so it falls short of full routing guidance.

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