get_chembl_molecule

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states it performs a search, but does not describe return behavior, potential multiplicity, rate limits, or read-only nature. This lack of detail leaves the agent uncertain about side effects and result scope.

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 brief and well-structured, with a single-sentence purpose followed by a clear Args section. Every word earns its place, and the information is front-loaded.

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 search tool with an output schema present, the description is mostly sufficient but has gaps: it does not specify what kind of results are returned (though the output schema may cover this), and it contains a slight inconsistency between 'SMILES' in the main description and 'ID' in the Args section, which could confuse the agent.

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 only defines the 'query' field as a string, and there are no schema descriptions (0% coverage). The description compensates by stating the query can be a compound name (with example 'aspirin') or ID, and the main description also mentions SMILES, adding practical meaning beyond the raw schema.

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 action ('Search'), the resource ('ChEMBL database'), and the object ('molecules and drugs'), with accepted input types ('name or SMILES'). It distinctly differentiates from sibling tools by targeting molecule/drug data rather than literature, protein structures, or gene info.

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 that this tool is for finding molecule/drug information via ChEMBL, which implicitly tells the agent when to use it versus sibling tools. However, it does not explicitly mention alternatives or exclusion cases, stopping short of the highest rating.

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