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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds a valuable behavioral note that 'Approved ANDAs indicate regulatory approval, not launch, supply, substitution, or market share.' This clarifies output interpretation beyond what annotations provide, though it could mention more about data freshness or rate limits.

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 sentences with no wasted words. The first sentence concisely states the purpose, and the second adds a critical caveat. It is front-loaded and 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?

Given the tool's complexity (2 parameters, output schema present, annotations rich), the description covers the core purpose and a key behavioral note. It does not address pagination or error cases, but with openWorldHint and a well-defined schema, this is acceptable.

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 (drug and limit). The description does not add new information about parameters beyond what the schema provides, so a baseline score of 3 is appropriate.

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 verb 'Profile' and the resource 'FDA Orange Book competition' for a specific input (ingredient or trade name). It lists the key outputs (matched applications/products, holders, RLD, patents, exclusivities) and includes a clarifying caveat about ANDAs. This distinguishes it from sibling tools like orange_book_product_search and orange_book_application_detail.

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 implies usage for profiling Orange Book competition but does not provide explicit guidance on when to use this tool versus alternatives. No when-not or alternative recommendations are given, though the context of Orange Book (small molecules) versus Purple Book (biosimilars) may be inferred from sibling names.

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