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 real behavioral context beyond that: this is live, mutating state that changes as connectors join/leave or capabilities are toggled, and it discloses a built-in steering default (most-stocked length). It omits auth/permission and response-format details, keeping it at a solid 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?

Front-loaded with the key claim ('LIVE catalog... no quote needed') and every clause carries real content about the return payload. The long parenthetical enumerations are dense but informative rather than filler.

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 carries the full burden of describing return contents and does so thoroughly: services ledger, gauge ladder, stocked hardware combos with lengths and shop counts, finish color menus, and process rules. Combined with the volatility warning, an agent has everything needed to invoke and interpret it.

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 single 'process' parameter is fully documented in the schema (100% coverage), which already explains it is advisory and that v1 returns the whole catalog regardless. The description adds no further parameter detail, so the schema-does-the-work baseline of 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?

States a specific verb+resource ('LIVE catalog of what the fabrication network can do') and enumerates exactly what it returns — services ledger, gauge ladder, stocked hardware, finish colors, manufacturability rules. This clearly distinguishes it from siblings like get_material_guide, get_shop_gauges, and get_fabrication_quote.

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?

Gives explicit context for use: 'call it fresh when the user asks what's possible (materials, gauges, hardware, colors, services) rather than answering from memory,' and distinguishes it from quoting flows via 'no quote needed.' It does not name a specific alternative sibling to use instead, so it falls short of a full when/when-not routing statement.

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