get_drug_pharmacovigilance

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

The readOnlyHint annotation already declares a safe read operation, and the description's 'Summarise' is consistent. The description adds the 'high-level' qualifier, implying a summary rather than granular data, but does not disclose what specific pharmacovigilance data is included or how results are structured. No contradiction with annotations.

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 unnecessary words. It immediately states the action and object, making it highly concise and well-structured for a simple tool.

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?

For a single-parameter, read-only tool with an output schema, the description covers the essential purpose adequately. It clearly indicates what the tool does, and the output schema handles return details. However, the lack of parameter explanation and the vague 'pharmacovigilance data' could be slightly more explicit, though not critical for this simple tool.

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 schema has 0% description coverage for chembl_id, and the description does not mention or explain the parameter. While chembl_id's meaning may be inferable from the tool name, the description provides no value beyond the schema, failing to compensate for the low coverage.

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 uses a specific verb 'Summarise' and a specific resource 'pharmacovigilance data for a drug', clarifying the tool's scope. The term 'high-level' helps distinguish it from detailed event tools like get_drug_adverse_events, though it does not explicitly name alternatives.

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 sibling tools such as get_drug_adverse_events or get_drug_pharmacogenomics. There is no mention of context, exclusions, or alternatives, leaving the agent to infer usage from the tool name alone.

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