search_drug_by_brand_name

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

No annotations are provided, so the description must carry the responsibility for disclosing behavior. The verb 'search' implies a read-only operation, but the description adds no other behavioral context such as exact-match behavior, pagination, or permission requirements. It is minimally transparent but not misleading.

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 a single, front-loaded sentence that states the exact operation and target. Every word is necessary, with no filler or duplication of schema details.

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?

Given the tool's simplicity and the presence of a comprehensive schema and output schema, the description is adequate for an agent to understand the tool's role. It does not explain the default language/format or status filtering, but those are covered by parameter descriptions. Missing a bit of usage context compared to sibling tools, but still sufficient within the larger toolset.

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 has 100% coverage with descriptions for all four parameters. The description only reiterates 'brand name', adding no additional meaning or context beyond what the schema already provides. With full schema coverage, a baseline score of 3 is appropriate.

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 uses a specific verb 'search' and a clear resource 'drug products' with a distinguishing modifier 'by brand name'. This uniquely identifies the tool among siblings like search_drug_by_din and search_active_ingredients, making its purpose unmistakable.

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 'by brand name' provides clear context for when the tool should be used: when the agent has a brand name to search for. However, it does not explicitly contrast with alternative tools or state when not to use it, though the sibling names largely convey those distinctions.

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