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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds useful behavioral context beyond annotations: it clarifies that search covers only public content and that results contain stable identifiers intended for exact public retrieval, which helps the agent understand how to use the output.

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 two concise sentences with no redundant wording. It front-loads the tool's broad purpose and then adds a valuable note about stable identifiers, making every sentence purposeful.

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?

For a simple one-parameter read-only search tool with a rich output schema and annotations, the description is largely complete. It conveys scope, public availability, and the nature of returned identifiers. It could marginally improve by mentioning pagination or result limits, but these are not essential for correct invocation.

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 already describes the single 'query' parameter with examples and constraints, so the schema carries the full parameter burden. The description does not add additional parameter-level semantics, so a baseline score of 3 is appropriate given the 100% schema description coverage.

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 states a specific action ('broad connector discovery') and resource scope ('public Vitals Vault biomarkers, panels, developer documentation, and comparisons'). It clearly conveys what the tool searches across, though it does not explicitly differentiate itself from sibling search tools like search_biomarkers or search_lab_catalog.

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 phrase 'broad connector discovery' implies this is the general-purpose search across multiple Vitals Vault content types, which gives some guidance on when to use it. However, it does not explicitly state when to prefer this over the more targeted sibling search tools, nor does it mention exclusions.

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