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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), lowering the burden. The description adds value by disclosing that the data is 'public' (no auth or user-specific context) and by specifying the breadth of the return payload, including URLs for ordering and Markdown pages, which an agent would otherwise not know without an output schema. No contradiction with annotations.

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?

One dense sentence front-loads the core function and then uses a colon-led list to enumerate return contents efficiently. Every element earns its place, and the enumeration is especially justified given the absence of an output schema.

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 burden of explaining return value composition, and it does so thoroughly across pricing, labs, prep, panels, FAQ, conditions, and URLs. Combined with strong annotations and fully documented parameters, an agent has everything needed to select and invoke this tool correctly.

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%, so both slug and lang are already documented, including the example values 'tsh' and 'general-wellness-panel'. The description confirms that the slug accepts an id and mentions the language option only indirectly through 'Spanish prose' context; it does not add material parameter meaning beyond the schema, so baseline 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?

The description opens with a specific verb and resource ('Full public detail for one TestWell test or panel') and names the lookup key ('by slug or id'). The enumerated content fields (biomarkers, CPT, per-lab prices, labs, fasting/prep, turnaround, FAQ, related conditions) make the scope unmistakable and clearly distinguish it from siblings like search_tests, list_panels, and compare_prices.

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 usage context is implied: this is the tool for full detail on a single test/panel, contrasted with list_panels for browsing or compare_prices for pricing comparisons. However, the description never explicitly names an alternative or states when not to use it; the routing hint that slugs come from search_tests lives in the input schema, not the description.

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