fda_covid_serology

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

The annotations include readOnlyHint=true, and the description consistently describes a search operation. It adds context about the data content (sensitivity/specificity, sample material, manufacturer) and count fields, which is useful beyond the annotation. It does not mention rate limits or result format, but that is a minor gap given the read-only nature.

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 compact and front-loaded: one sentence stating the main purpose, two example queries, and one line mentioning count fields. Every sentence contributes meaningfully, with no redundancy or fluff.

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 two-parameter search tool with no output schema, the description covers the core purpose, provides usage examples, and highlights count fields. It lacks explicit details about result structure or pagination, but these are not critical for a straightforward search API and the provided information is sufficient for initial use.

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 100% with descriptions for both parameters. The description adds value by giving concrete example field values (e.g., 'antibody_truth:"Positive"' and 'manufacturer:"Abbott"') and listing count fields, which enriches the understanding of how to construct queries.

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 'Search COVID-19 serology test evaluation results', specifying the verb and resource. It further clarifies it covers FDA's antibody test performance (sensitivity/specificity), which distinguishes it from other FDA tools like fda_drug_events or fda_device_clearances.

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 provides clear context about what the tool searches and includes example queries to guide usage. However, it does not explicitly state when to use this tool over alternatives or when not to use it, making it solid but not fully explicit.

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