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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds valuable behavioral context by noting that the data is 'scraped from the herb's EMA page' and that it returns direct PDF links, which goes beyond the annotations.

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 front-loaded with the core purpose and includes example queries at the end. It is slightly verbose but every sentence contributes value, with no wasted words.

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?

There is no output schema, but the description lists the returned fields (botanical names, therapeutic areas, assessment status, outcome, dates) and the PDF links. It lacks details on error handling or mutual exclusivity of parameters, but it is sufficiently complete for a single-herb lookup tool.

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?

The input schema fully describes both parameters with examples, and the description reiterates that lookup is by Latin or English common name. It does not add details about precedence if both are provided, but with 100% schema coverage, the 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 tool's purpose: retrieving a full EMA herbal-inventory record for one plant/herb, including monograph and assessment-report PDF links. It specifies the lookup by Latin or common name and gives concrete example queries, making it distinct from sibling tools like herb_search or herb_monograph_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?

The description provides clear context through example queries that indicate when to use it (e.g., for obtaining monograph links or assessment reports). However, it does not explicitly mention alternatives or conditions where this tool should not be used, so it stops short of full usage guidance.

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