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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value-add is the content manifest and the explicit non-capabilities — genuinely useful for a zero-arg tool. It stops short of stating anything about data freshness, pricing currency, or volatility, which matters for a pricing-adjacent tool.

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?

Three functional sentences: what it returns, when to call it, what it does not do. Content manifest is front-loaded, the routing exclusions trail. No filler or restatement of the title.

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 and no parameters, the description carries the return-value burden and does so by enumerating the information returned. A note on whether pricing is static or current, and in what form it arrives, would close the last 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 input schema is an empty object with zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless, no-argument invocation.

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?

Specific verb + resource ("Get authoritative 3D2HOLO product information") with an enumerated content payload: workflows, input types, output formats, LPI range, resolution, pricing. The scope sentence explicitly separates it from the four siblings' capabilities, so an agent can route between them without opening schemas.

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?

States the exact triggering condition ("when the user asks what 3D2HOLO supports or how much the service costs") and adds a behavioral directive against hallucinating capabilities ("instead of relying on remembered or assumed capabilities"). The exclusion list implicitly routes compute/calibration/quote questions to calculate_output_params, generate_pitch_test_chart, and get_print_quote.

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