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

With empty annotations, the description must disclose behavioral traits. It only states 'openFDA food enforcement' without indicating whether the tool is read-only, whether it returns data, or any constraints like rate limits or pagination. This provides no actionable behavioral context.

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?

While extremely short, the description is under-specified rather than concise. It lacks structure, front-loading minimal domain information without any useful content. Every word should earn its place, but here they are too sparse to be helpful.

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 the absence of output schema and the complexity of food enforcement data, the description is completely inadequate. It does not explain return values, optional parameters, or any other details needed for correct invocation. The tool is essentially opaque.

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%, yet the description adds no meaning to the 'query' parameter. It does not explain what types of queries are accepted, expected format, or how it affects results. The tool name alone does not compensate.

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 'openFDA food enforcement' vaguely indicates the domain but fails to specify the action (e.g., search, list, get). It does not distinguish this tool from siblings like 'food_recall_check' or 'drug_recalls' which have more specific names and purposes.

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 guidance is provided on when to use this tool over alternatives. There is no mention of context, prerequisites, or exclusions, which is critical given the many related sibling tools in the food/recall domain.

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