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

Beyond the readOnlyHint and destructiveHint annotations, the description adds significant behavioral detail: it explicitly states that the tool runs a real Plant Builder engine and includes an anti-fabrication directive to quote numbers verbatim. It also discloses the internal system mechanics (DES schedules campaigns/injects failures, DRS solves continuous flow, bridge couples them), which the annotations do not cover.

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 efficiently structured: it opens with the primary action, follows with a concise breakdown of the three-system series, lists the specific return data, and ends with an important behavioral note. Every sentence adds value without redundancy, keeping the description compact yet comprehensive.

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 that there is no output schema and no parameters, the description carries the full burden of explaining what the tool returns and what it does. It thoroughly specifies the plant rollup metrics, per-product attainment, and per-system timelines, making it complete for an agent to decide on invocation and interpret results.

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?

With zero parameters in the schema, the baseline is 4 per the rubric. The description correctly implies that no inputs are needed and does not need to add parameter details. It also indirectly confirms this by focusing entirely on the run and its outputs.

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 verb 'Run' and the target resource 'Chocolate Processing (CHOC) demo', distinguishing it from sibling run_* tools by detailing the DES↔DRS bridge topology and its three-system series. It also enumerates the specific outputs, leaving no ambiguity about what the tool does.

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 provides clear context by explaining the demo's focus on the joint DES↔DRS bridge and that it exercises all 7 controllers + Goal blocks, which implies when to use this tool (when a comprehensive chocolate process demo is needed). However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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