search_formulary

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

No annotations are provided, so the description must fully disclose behavior. It mentions that the tool returns 'structuredContent' and specifies fields to preserve, hinting at a read-only search operation. However, it does not cover auth requirements, rate limits, or any destructive potential.

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 extremely concise: one sentence for purpose and one sentence for usage guidance. It is front-loaded with the core action and provides essential instructions without waste.

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 presence of an output schema (which documents return values), the description adequately covers the tool's operation, including how to handle results. It misses potential details like pagination or error handling, but overall is sufficient for a search tool.

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 50% (two of four parameters have descriptions in the schema). The tool description adds no additional parameter meaning beyond the schema. It focuses on output handling, not input semantics.

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 'Search hospital formulary by drug name or code' uses a specific verb and resource, making the tool's purpose clear. It is distinguishable from siblings like 'search_drug' which likely searches a broader drug database.

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 description provides an 'agent contract' instructing how to handle the output (preserve fields, not infer facts), but does not explicitly state when to use this tool versus alternatives like 'search_drug' or 'get_drug_info'.

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