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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds context about what the tool returns (bibliographic record and tagged targets/diseases) and how evidence tier is assigned. It does not mention pagination, limits, or potential variations in output, but for a single-record lookup the provided information is adequate.

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 fluff. The core functionality is front-loaded, and the usage hint is appended succinctly. Every word adds value, making it an efficient and well-structured definition.

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?

For a simple one-parameter read tool, the description covers what is returned, how the evidence tier is tagged, and where to obtain the required id. With no output schema and annotations covering safety, this is sufficient. Minor gaps like error handling or edge cases are not critical for this type of 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?

Schema coverage is 100% with paper_id described as a HERB reference id. The description reinforces the format with an example (HBREF000003) and clarifies the source of the id, adding value beyond the schema. Since coverage is high, the baseline is 3, and the description provides extra semantic guidance, earning a 4.

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 a reference's bibliographic record plus specific targets/diseases with evidence tier. It specifies the exact fields (journal, PubMed id, experiment type, phenotype) and how evidence tier is derived. While it doesn't explicitly name sibling tools, the mention of 'herb_detail' and 'herb_papers' as sources for the paper id provides some differentiation context.

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 gives guidance on where to obtain the paper_id (from drug_paper_target/drug_paper_disease rows or herb_papers), which is useful for invocation. However, it does not explicitly state when to use this tool versus alternatives like herb_experiment_detail or herb_papers, nor does it mention when not to use it. The usage context is implied but not fully articulated.

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