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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: a GtoPdb API key is required, where to register, and that it must be passed via _apiKey. It stops short of noting rate limits or pagination behavior.

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?

Purpose and scope are front-loaded in the first clause, followed by return shape, then the required follow-up tool and auth instructions. Dense and mostly waste-free, though the trailing 'Complements ChEMBL/DrugBank' clause is a slightly dangling addition.

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 no output schema, the description supplies the return fields and their meaning; it also covers the auth prerequisite and the downstream tool. For a two-parameter, read-only search tool, an agent has everything needed to call it 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?

Schema coverage is 100% for the two declared properties, so the baseline is 3. The description goes further by documenting the _apiKey parameter (which appears only in the schema examples, not in properties) and by describing the shape of the returned target record, adding meaning beyond the 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?

States a specific verb (Search) and resource (Guide to PHARMACOLOGY / IUPHAR-BPS protein targets by name), and describes exactly what comes back (GtoPdb target id, abbreviation, type). It is clearly distinguishable from siblings like search_ligands, ligand_interactions, and target_interactions.

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?

Explicitly routes the agent: 'Use the returned target id with target_interactions to find ligands that bind it,' and positions the tool as complementing ChEMBL/DrugBank. It gives clear positive usage context and the follow-up chain, but states no exclusion condition (when not to use it vs. other search tools).

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