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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: Class I recall implications (mandatory press releases, procurement review obligations) and an illustrative example that reveals output patterns. It does not mention pagination or date ranges, but the added context earns a solid 4.

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 moderately sized with several sentences, but each earns its place: use case, return types, Class I context, example, and source. It is front-loaded with the usage context and not overly verbose. Slightly long for a 1-5 scale, but efficient.

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?

The tool has no output schema, so the description carries the burden of explaining return values. It does so: recall classifications with descriptions and reasons, plus an example. It lacks parameter-level details and temporal scope, but for a simple two-parameter tool, it is largely complete.

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% and the description does not mention company_name or product_type parameters at all. The example implies drug recalls, but there is no explicit guidance on how to set product_type or which values to supply. With only 0% schema coverage, the description needed to compensate but did not.

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 returns FDA recall classifications with product descriptions and recall reasons, and frames it for evaluating companies for product safety risk. This specific verb+resource distinguishes it from related tools like get_drug_recall_status, which focuses on a narrower drug recall status.

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?

Explicitly states when to use: 'when evaluating a pharmaceutical company, medical device manufacturer, or healthcare vendor for product safety risk, supply chain exposure, or regulatory compliance standing.' It provides clear context but does not name alternatives or exclusions, which would be needed for a 5.

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