describe_plot_families

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

With no annotations, the description carries the full behavioral-disclosure burden. It discloses a non-obvious and important behavior: availability is judged by what a family asks the summary for, not by the columns it draws, and warns that checking drawn columns produces false 'missing columns'. This is substantive context beyond the basic function.

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?

Two sentences with the main purpose front-loaded and a valuable caveat in the second sentence. Every sentence earns its place, with no redundant wording.

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 zero-parameter descriptive tool with no output schema, the description gives the core purpose and the key correctness caveat. It does not specify the exact return format or prerequisites, but the most important contextual nuance is present.

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 tool has zero parameters and an empty input schema, so parameter semantics are trivially complete. The baseline of 4 for zero-parameter tools applies; no parameter explanations are needed.

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 what the tool does: summarize the plot families cellpy offers and report whether loaded cells support them. This specific resource—plot families plus cell support—distinguishes it from siblings like describe_api and list_cells.

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?

The description implies the tool is used after cells have been loaded and references summary_options().columns, but it does not explicitly state when to prefer this tool over describe_api or other alternatives. Usage context is present but mostly implicit.

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