get_target_safety_information

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

The annotations declare readOnlyHint=true, and the description's verb 'Retrieve' is consistent, so there is no contradiction. However, the description adds no extra behavioral context beyond the annotation—no mention of data sources, rate limits, or output structure.

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 concise sentence that front-loads the action and resource, with no unnecessary repetition.

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 with one parameter and an output schema, so basic retrieval is covered. However, it lacks guidance on use cases or what constitutes 'safety liabilities,' and does not differentiate from many sibling target tools.

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%, and the description does not explain the ensembl_id parameter. It only refers to 'a target,' implying the parameter identifies the target, but gives no format or example. The parameter name is self-explanatory, but the description offers minimal added value.

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 ('Retrieve') and the resource ('documented safety liabilities' for a target), which is distinct from sibling tools like get_target_info or get_target_known_drugs. The phrasing is specific enough to convey that this returns safety-related liability data for a given target.

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 explicit guidance is given on when to use this tool versus alternatives such as get_target_info or get_target_tep. The context implies usage when safety liability information is needed, but it does not mention exclusions or alternative tools.

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