pharmacophore_view

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

The description details the visual output comprehensively: color coding for atoms, H-bond dashes, residue sticks, pocket surface, and backbone cartoon. No contradictory or missing behavioral info.

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 front-loaded with the main purpose, then a clear bullet-like list of visual features, followed by parameter definitions. Every sentence adds value without redundancy.

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 output schema existence (not needed for return values) and the lack of annotations, the description fully covers what the tool does visually. No missing context for a visualization 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, but the description adds examples and clarifies each parameter's role (obj_name as Python object name, resn as ligand residue name). This compensates well.

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 colors a ligand by pharmacophore feature type. It provides a specific verb and resource, distinguishing it from generic visualization tools.

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?

There is no guidance on when to use this tool versus alternatives like ligand_view or pocket_view. The description only explains what it does, not when to apply it.

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