get_target_class

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

Annotations already provide readOnlyHint=true, and the description simply restates the read-only nature without adding additional behavioral context such as error handling, data coverage, or prerequisites. No new information beyond the annotation and the tool's name is disclosed, so the description adds minimal value for transparency.

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 a single, front-loaded sentence with no filler or repetition. Every word ('Return', 'ChEMBL target class annotations', 'gene') earns its place, making it maximally concise and well-structured.

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 only one parameter, a readOnlyHint, and an output schema present, the tool is simple. The description sufficiently conveys the core purpose, and the output schema reduces the need to explain return values. However, a brief note about the expected format of ensembl_id would make it fully complete given the lack of schema descriptions.

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 0%, so the description bears the burden of explaining the parameter. It only says 'for a gene', which is redundant with the parameter name ensembl_id. It does not clarify that Ensembl gene IDs typically follow a format like ENSG000001..., nor does it explain what the identifier represents beyond 'gene'.

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 'Return ChEMBL target class annotations for a gene' uses a specific verb ('Return') and a clear resource ('ChEMBL target class annotations') scoped to a gene. This clearly distinguishes it from sibling tools like get_target_info or get_gene_ontology_terms by the specific type of annotation returned.

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 usage when a gene's ChEMBL target class is needed, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or alternatives among the many sibling get_target_* tools, leaving the agent to infer applicability from the resource name.

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