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

No annotations exist, so the description carries full burden. It discloses monthly refresh and a per-call price, but does not mention destructive behavior, authentication requirements, rate limits, or pagination details. Useful but not comprehensive.

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 with no wasted words: states action, answers question, mentions refresh and price. Front-loaded with the key purpose.

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 7 parameters, no annotations, and no output schema, the description is too brief. It omits output format, interaction between search fields, and pagination behavior. Adequate for a simple query but not fully complete.

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 0%, so the description must compensate. It lists searchable fields (name, NPI, state, exclusion type), but the schema has 7 parameters including offset, limit, last_name_search, business_name_search. The description adds meaning for 4 but leaves offset, limit, and the distinct name fields unexplained.

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 searches the OIG List of Excluded Individuals/Entities (LEIE) by various criteria, answering a specific question about provider exclusion. It distinguishes from sibling tools like sanctions_screen by focusing on the LEIE 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 implies usage for checking provider exclusion status but does not explicitly state when to use this tool versus alternatives like sanctions_screen. No exclusions or when-not-to-use guidance is provided.

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