检查用药安全和忌口提醒

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

No annotations provided. Description only lists checked items but does not disclose behavioral traits like read-only nature, required permissions, or what happens if parameters are omitted. Insufficient for a tool with no 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?

Single sentence is concise but lacks structure and front-loads limited info. Could be improved by adding parameter context while maintaining brevity.

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 annotations, description should cover return format, parameter usage, and prerequisites. It does not, leaving significant gaps.

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 0%, and description does not explain parameters ddinterIds or includeDdinter. Agent must rely solely on parameter names and schema, which is inadequate.

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?

Description clearly states it checks allergies, duplicate medications, DDInter interactions, and drug-food restrictions. Verb and resource are specific, and it distinguishes from siblings like ddinter_check_interactions which focuses only on DDInter.

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?

No guidance on when to use this tool versus alternatives like ddinter_check_interactions or health_allergy_list. Agent cannot determine best tool for a specific sub-check.

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