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

No annotations provided, so description carries full burden. It mentions price ($0.03/call) and implies read-only search, but does not disclose pagination behavior, rate limits, or authentication needs. The description adds some context but is missing behavioral details beyond what is inferred.

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 three sentences plus a price note—concise and front-loaded. Every sentence adds value: purpose, use case, filters, and pricing. No wasted words.

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 8 parameters and no output schema, the description is adequate but incomplete. It explains the tool's purpose and filters but does not describe the return format, pagination details, or error behavior. It covers the main context but leaves 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 75% (6 of 8 params have descriptions). The description adds contextual meaning, e.g., 'has_npi' for joining provider graph, but does not cover limit and offset. It provides some added value but does not fully compensate for the uncovered 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 it searches HRSA 340B OPAIS covered entities and child sites by state, entity type, or name. It distinguishes from siblings by specifying '340B' and mentioning entity type codes like FQHC/DSH/CAH. The purpose is precise and unambiguous.

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 answers the use case: which 340B-eligible entities operate in a territory and which have NPIs. It lists filters but does not explicitly contrast with sibling tools or state when not to use. The context is clear but lacks exclusion guidance.

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