fda_covid_serology

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

Annotations already provide readOnlyHint=true, so the description's behavioral disclosure is not critical. The description adds that it returns evaluation results (sensitivity/specificity) but does not elaborate on pagination, rate limits, or data freshness. With annotations covering safety, the description provides moderate additional context, justifying a 3.

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 succinct with four sentences. The first sentence states the purpose, the second provides context, the third offers concrete examples, and the fourth lists key count fields. No redundant information, and critical details are front-loaded.

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 no output schema and only two parameters (search, limit) with full schema coverage, the description is adequate. It explains the tool's domain, provides search examples, and notes aggregation fields. It could mention output format or pagination, but the examples and count field hint are sufficient for a straightforward search tool with readOnlyHint.

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?

While schema coverage is 100% and both parameters have descriptions, the description adds value by providing tool-specific example queries (e.g., 'antibody_truth:"Positive"') and mentioning count fields for aggregation. This enriches the schema's generic 'search query' description, making it more actionable for the agent.

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 COVID-19 serology test evaluation results, specifically FDA's evaluation of antibody test performance (sensitivity/specificity). The verb 'search' and resource 'FDA serology evaluations' are explicit, and it distinguishes from sibling FDA tools by its unique focus on serology.

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 helpful example searches and notes count fields, which guides usage. However, it lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools (e.g., other FDA search tools). There is no mention of alternatives or exclusions, leaving the agent to infer context from the tool name alone.

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