set_active_plot

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does well by explaining fuzzy matching, folder-name mapping, and the rule for choosing the most recently-modified XML. It does not describe failure behavior or persistence, but the core state-changing behavior is clearly stated.

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 short, front-loaded, and contains no filler. Every sentence contributes useful information: the action, the matching behavior, the examples, and the file-selection rule.

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 one-parameter setter with no annotations, the description is largely complete. It explains the operation, matching, and selection logic. Minor gaps remain around no-match or ambiguous-match behavior, but the presence of an output schema reduces the need to document return values.

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 description coverage is 0%, so the description must compensate for the bare input schema. It does: show_name is defined as fuzzy-matched against folder names, and examples clarify expected inputs. This adds meaningful semantic value beyond the schema.

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 states a specific verb and resource: 'Switch the active plot by show name.' It also clarifies the selection mechanism (fuzzy-matched against folder names, most recently-modified XML), which distinguishes it from sibling tools like set_active_file.

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 gives clear context for when to use the tool: when the active plot should be selected by show name. It does not explicitly name alternatives or exclusions, such as 'use set_active_file for direct file selection,' but the intended use case is clearly implied.

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