US Drug Shortages (FDA) MCP

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

No annotations exist, so the description carries the full burden. It does disclose meaningful behavior: batch limit of 100 drugs and (via 'PRO') a paid/subscriber tier tied to access_token. It does not say what happens beyond 100 drugs, whether partial failures are tolerated, or the shape of the result.

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 tightly worded fragments with the batch constraint front-loaded; nothing is padded. The leading 'PRO.' token is a bit cryptic and not self-explanatory, but it costs little space.

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?

With no annotations and no output schema, the description should explain what comes back (e.g., per-drug shortage status) and any subscription/auth prerequisites. It covers input scope well but leaves the response contract and auth requirement implicit, which is a notable gap for an unannotated 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 coverage is 50%: access_token is documented in the schema itself, and the description adds real meaning to 'drugs' (a formulary/stock list of drug names, max 100 items). The formula for the drugs array (names vs IDs, matching tolerance) remains unspecified in both places.

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?

States a specific verb (check) and resource (drugs against FDA shortages), with the batch scope ('up to 100 drugs') made explicit. It does not name or contrast with the siblings shortage_check and shortage_list, so an agent can't tell why to pick this over shortage_check without further inference.

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 when-to-use guidance and no mention of the sibling alternatives (shortage_check, shortage_list). The 'PRO' prefix hints at a premium/bulk variant but gives no explicit condition for selecting this tool instead of the others.

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

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

There are no annotations, so the description carries the full behavioral burden. It does add useful context such as 'FREE' and that results cover the top 3 presentations, but it omits details like read-only guarantees, auth requirements, rate limits, and exact return semantics.

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 two compact sentences with no waste. 'FREE' is front-loaded, and the core question plus output scope follow immediately.

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 simple one-parameter read tool, the description is mostly sufficient for invocation. Without an output schema or annotations, however, it should say more about what the shortage status response contains beyond 'top 3 presentations,' such as status values or not-found behavior.

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 coverage is 0%, so the description must compensate for the undocumented 'drug' parameter. It does so by stating that a generic or brand name is accepted, which is meaningful parameter guidance beyond the bare schema string type.

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 states a specific question and resource: checking US FDA shortage status for a drug, with generic or brand name accepted. It implies scope via 'top 3 presentations,' but does not explicitly distinguish itself from sibling tools such as shortage_list.

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?

Usage is implied by the question format: use this when checking a specific drug. However, there is no explicit guidance on when to use this instead of shortage_list or formulary_watch, and no exclusions or prerequisites are stated.

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

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

No annotations are provided, so the description carries the full disclosure burden. 'PRO.' plus the access_token parameter implies a paid-subscriber requirement, which is useful signal, but nothing is said about result volume, pagination, rate limits, or whether the list is exhaustive — significant gaps for a bulk-listing tool.

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 short sentences with the core scope front-loaded and zero padding. The cryptic 'PRO.' token is the only piece that does not clearly earn its place without explanation.

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 zero-required-parameter read tool with no output schema and no annotations, the description covers scope and the category filter adequately. It still leaves return shape, result volume, and the meaning of the PRO/access_token requirement unaddressed, which matters more here because no structured field supplies that context.

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 coverage is 67%: status and access_token are described in the schema, while category has no schema description — the description compensates with concrete examples ('Oncology', 'Anesthesia'). However, the description only mentions current/resolved status values and omits 'To Be Discontinued', and says nothing about category matching semantics (exact vs. partial).

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?

States a specific resource (shortages) and scope (all current or resolved, optionally filtered by therapeutic category), which an agent can grasp immediately. It does not explicitly differentiate itself from the sibling shortage_check (presumably a single-item lookup), so sibling disambiguation is left to inference.

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 word 'optionally' hints that the category filter is elective, but there is no statement of when to use this versus shortage_check or formulary_watch, nor any prerequisites beyond the implicit PRO tier. The 'PRO.' prefix is unexplained, so an agent cannot tell whether it gates access.

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