store_entities

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

The description confirms a mutating write ('Store') and the annotations show readOnlyHint=false, so there is no contradiction. It also adds useful context about accepted entity types and the extraction workflow. However, it doesn't disclose storage semantics such as whether re-storing the same DOI merges, replaces, or duplicates entities; this gap is notable given the idempotentHint=false annotation.

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?

Four short sentences, each with a distinct job: purpose, trigger, type vocabulary, and input shape. The most important information is front-loaded, and there is no filler or repetition.

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?

With one parameter, an existing output schema, and low overall complexity, the description is largely complete for selecting and invoking the tool. It provides the trigger, data shape, and allowed entity types; the main residual gap is the lack of merge/replace/duplicate semantics, but that is not required to make a correct first call.

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 schema provides 0% description coverage and only says 'results' can be a string or an array of empty items. The description fills this gap by specifying the expected payload shape—'list of {doi, entities: [{name, type}]}'—and enumerating valid entity types. It is slightly under-specified because it doesn't mention the allowed string form or exact doi format, but it gives enough to construct a valid call.

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 opens with a specific action and object: 'Store extracted biomedical entities for papers.' This clearly distinguishes it from siblings like search_entities (retrieval) and get_unextracted_abstracts (extraction), letting an agent tell what the tool is for without opening the schema.

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?

It explicitly states when to call: 'Call this after extracting entities from abstracts (via get_unextracted_abstracts or any paper reading).' This gives a clear workflow condition and names a prior step. It doesn't list exclusions, but there is no obvious alternative tool for persisting entities, so the guidance is sufficient.

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