hvplot_get

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

Description reveals behavioral traits: returns only plot-specific parameters by default, offers optional generic and style expansions, and equivalence to hvplot.help(). No annotations provided, so description carries full burden. No discussion of limitations or side effects, but acceptable for a help tool.

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?

Four sentences, efficient and well-structured. First sentence states main purpose, subsequent sentences detail options. No filler or 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 output schema exists (not shown), description adequately covers all functionality: compact vs full, signature option, and equivalence to hvplot.help(). No missing context for effective invocation.

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 coverage is 100%, baseline 3. Description adds meaning by explaining that generic and style control output breadth, and signature changes output type. It also provides example plot_type values ('line', 'scatter').

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?

Description clearly states the tool retrieves the hvPlot docstring or signature for a specific plot type. It distinguishes from siblings by using 'hvplot' prefix and referencing hvplot API, differentiating from hvplot_list and hv_get.

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?

Description explains when to use compact output (default) vs full docstring with generic and style parameters, and that signature=True returns signature. It lacks explicit when-not-to-use but provides clear usage context.

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