search_chembl_id_lookup

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

Without annotations, the description adds the return format (JSON string) and the fact that multiple parameter names are accepted. However, it does not disclose any potential side effects, authentication needs, or limitations, which is a gap for a search tool.

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 to the point, with the purpose front-loaded. The list of parameter aliases is useful but could be integrated more naturally. Overall, it is concise without unnecessary details.

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?

Given the tool has 8 parameters and many similar siblings, the description lacks details on default behavior, required vs optional parameters, output schema, and how to avoid redundant parameter usage. It does not fully equip the agent to use the tool correctly.

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 description adds significant value by listing all eight alternative parameter names and identifying `query` as the canonical one. This compensates for the low schema description coverage (25%), helping the agent understand the parameter flexibility.

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 searches for a ChEMBL ID by query. The name and verb are specific, but it does not differentiate from similar sibling tools like search_chembl_molecule or search_chembl_target, leaving ambiguity about when to use this specific tool.

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?

No guidance is provided on when to use this tool versus its siblings. It only lists alternative parameter names without explaining the preferred usage or context, leaving the agent without decision support.

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