get_formulary_item

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

With no annotations, the description carries full burden. It adds a clear 'Agent contract' specifying that structuredContent is the source of truth and that certain fields must be preserved. This provides crucial behavioral context beyond the basic read operation, though it omits details like authentication requirements or rate limits.

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 with two sentences. The first sentence states the purpose, and the second provides critical behavioral instructions. Every word adds value with no redundancy.

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 that an output schema exists and many sibling tools are listed, the description provides essential information for a simple lookup tool. It covers the key behavioral contract and clarifies the input parameter. Minor lack of usage guidance and sibling differentiation prevents a perfect score.

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 67% description coverage (locale and output_format have descriptions, drug_code does not). The description clarifies that drug_code is the lookup key, compensating for the missing schema description. It does not add further semantics for the other parameters.

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 clearly states the tool retrieves hospital formulary item details by drug code. However, it does not differentiate from sibling tools like 'search_formulary' or 'get_drug_info', which could cause confusion about when to use this specific tool.

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. The description lacks any 'when to use' or 'when not to use' hints, relying solely on the tool's name to imply its purpose.

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