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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds beyond these by detailing the exact return values (throughput percentages, binding bottleneck, converter/storage detail) and includes an explicit anti-fabrication directive ('quote verbatim'), which is a valuable behavioral caveat.

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 moderately detailed but every sentence adds value: line composition, decision set, output specification, interpretive insight, and a data-source warning. It is front-loaded with the action verb and specific percentages, though slightly longer than strictly necessary.

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 there is no input schema (0 parameters) and no output schema, the description fully covers the tool's behavior: it states what is returned (throughput percentages, bottleneck, detail) and includes a behavioral rule. This makes it self-contained for a demo tool.

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, the baseline is 4. The description clarifies that the three 'strategic decisions' are internal scenarios, not inputs, and the empty schema requires no additional parameter documentation.

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 opens with 'Run the Tissue Line (TIS) demo' — a specific verb and resource. It further specifies the line configuration (Reel supply → Converter → Winder) and the three strategic decisions, distinguishing it from sibling demo tools like run_chocolate_processing or run_valdez_tanker.

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?

It clearly identifies the demo's focus ('sim-foundation parameter-set example') and describes the decision scenarios. The concluding insight ('invest at the constraint') suggests when this tool is pedagogically useful, but there is no explicit statement of when to use this over other run_* siblings.

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