hide

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

No annotations are provided, so the description is the sole source of behavioral info. It discloses only the basic action and lacks details about reversibility, side effects, or selection defaulting to 'all'. The agent cannot tell if hidden representations are merely toggled off or if there are any lasting consequences.

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. It is appropriately concise for a simple tool, though it sacrifices informative detail that would improve other dimensions.

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 has an output schema and fully described parameters, so the description need not cover return values. It adequately states the core function, but the absence of usage context, exclusions, and behavioral detail—compounded by missing annotations—leaves the description minimally viable rather than complete.

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?

Both parameters have schema descriptions, giving 100% schema coverage. The description adds no meaningful parameter semantics beyond the schema; 'given selection' is already captured by the schema's 'PyMOL selection string.' Baseline 3 applies.

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: 'Hides a graphical representation for a given selection.' It identifies the resource (graphical representation) and the scoping (selection). It does not explicitly differentiate from sibling tools like delete or remove, but the verb 'hide' conveys a visibility toggle rather than destruction.

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 alternatives such as show, delete, or remove. The description merely states the action without context, exclusions, or alternative tool recommendations.

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