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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description contributes only the underlying endpoint (GET /search), which does not inform agent behavior — no result format, ranking/truncation behavior, or rate limits are described.

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?

Two short sentences, front-loaded with the core purpose. The trailing 'Engine API: GET /search' is arguably low-value for an agent selecting a tool, but it costs little space.

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 seven parameters (including a nested object), no output schema, and no explanation of what a returned concept looks like or how results are meant to be used downstream, the description is thin for the tool's complexity. An agent gets no sense of the return payload despite the absence of an output schema.

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 all seven parameters (age, sex, types, phrase, dev_mode, model_id, max_results) are documented in the schema itself. The description adds nothing about parameter semantics, which is acceptable at the 3 baseline when the schema does the heavy lifting.

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 and resource — search the medical concept database for observations matching a phrase — and frames it as autocomplete, which tells the agent what kind of lookup this is. It does not, however, distinguish itself from the many sibling lookups (list_symptoms, get_symptom, parse, suggest), leaving the agent to infer the boundary.

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 parenthetical '(autocomplete)' implies a partial-phrase lookup scenario, but there is no explicit when-to-use guidance, no statement of when to prefer this over list_* / get_* siblings, and no mention of prerequisites or follow-up steps.

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