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

The readOnlyHint annotation already conveys the safety profile; the description adds context about cross-catalog synthesis and the kind of output expected (missing artifact types). It does not disclose any side effects or edge-case behavior, but for a read-only analysis tool this is acceptable and non-contradictory.

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 short and front-loaded with the core purpose, followed by pricing context. The pricing sentence is useful for selection but not strictly necessary for invocation, so it is concise but not maximally tight.

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 Ring, the description does not explain the return value shape, pagination, or how results are structured. It also leaves required slug semantics implicit and does not distinguish itself operationally from the sibling gap_analysis tool, which is a meaningful completeness gap.

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 schema already documents context and min_share, and the description's 'whole industry' language implies that slug refers to an industry, but the required slug parameter is left undocumented in the schema and the description does not explicitly clarify how to obtain or format it. The description provides some inferable meaning but does not fully compensate for that gap.

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 states the tool's resource and scope: it identifies valuable artifact types (MCP, Arazzo, Rules, Skills…) that are commonly missing across an industry. The phrase 'whole industry' differentiates it from company_gaps and generic gap_analysis, though it lacks an explicit action verb like 'find' or 'analyze'.

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 gives clear context for when to use the tool: 'across a whole industry' and 'where the vertical is under-served' signal an industry-level, cross-catalog analysis rather than a company-specific one. It does not explicitly name alternatives or exclusion conditions, but the scope is unambiguous.

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