Save Drug Research

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

Annotations exist but are minimal (readOnlyHint=false, destructiveHint=false). The description adds that it validates and caches data, and returns a medication check result. It does not elaborate on side effects or required permissions.

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 sentences totaling 20 words, conveying the purpose, actions, and output. No redundant or extraneous information. Excellent conciseness.

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?

The description explains the tool's actions (save, validate, cache) and output (medication check result). However, without an output schema, it would be beneficial to describe the return format. The annotations provide basic safety info.

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 coverage is 100% for the single parameter study_json. The description mentions validation, but the parameter description already states it must follow the OpenPGx schema. No additional semantic value beyond the schema.

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 explicitly states 'Save pharmacogenomic research from web search as a local study,' clearly identifying the verb and resource. It distinguishes from siblings like check_medication by focusing on saving research. However, it could be more specific about the scope.

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 is provided on when to use this tool versus alternatives like search_drug_pgx or check_medication. The description does not mention prerequisites or context for use.

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