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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds valuable behavior: it returns a specific set of fields, and for biologics it explicitly states the response will indicate no data rather than returning an empty list. This goes beyond the annotations and clarifies expected output.

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 filler. The first sentence front-loads the action and key parameters; the second sentence adds a critical edge-case clarification. Every word earns its place.

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?

The tool is simple (3 optional params, no required), has an output schema, and strong annotations. The description covers the tool's purpose, filters, return types, and an important edge case. This is sufficient for an agent to decide to invoke it and know what to expect.

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 description coverage is only 33% (only 'limit' is described). The description compensates by explaining that molecule_chembl_id and target_chembl_id are filters, and the word 'and/or' clarifies that either or both can be used. It does not add format details, but the semantic role is clear.

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 'Retrieve bioactivity records from ChEMBL filtered by molecule_chembl_id and/or target_chembl_id', which clearly states a specific verb and resource. It further specifies the returned data (IC50/Ki/EC50 values, assay descriptions, units) and distinguishes itself from sibling tools like chembl_mechanism, molecule, or target by focusing on bioactivity records with these filters.

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 when to use the tool (when you need bioactivity data for a molecule or target) but does not explicitly mention alternatives or exclusions. The note about small-molecule data provides context but not a direct comparison to other ChEMBL tools. There is no 'use this instead of X' guidance.

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