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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that the result includes exclusion/reinstatement/waiver dates and source freshness, but it does not disclose behaviors such as not-found handling or data-source caveats.

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?

One clear, front-loaded sentence that states the action, the scope, and the return contents with no filler. Every clause adds useful information.

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?

For a one-parameter, read-only tool with rich annotations, the description covers the input source and the output categories. Because there is no output schema, slightly more detail about the response envelope would make it fully complete, but it is sufficient for correct invocation.

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 100%, and the schema already documents exclusion_id as a 24-character evidence ID from a LEIE result. The description echoes this provenance without adding new format, validation, or value 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 uses a specific verb ('retrieve'), identifies the exact resource ('one HHS OIG LEIE exclusion record'), and specifies the key ('evidence ID returned from a LEIE lookup/search'). This clearly distinguishes it from sibling tools such as leie_search_exclusions and leie_lookup_npi.

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 clearly frames the tool as a follow-up to a LEIE lookup/search by requiring an evidence ID from those flows. It does not explicitly name alternative tools or state when not to use it, but the intended usage context is unambiguous.

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