jactus_run_example

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

No annotations present, so description fully handles transparency. Discloses subprocess execution, 30-second timeout, output components, and dependency on JACTUS source tree and env var. Adequately transparent.

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?

Concise yet informative: three short paragraphs covering purpose, usage note, and parameter. No redundancy, well-organized with natural reading flow.

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?

Has output schema (context), so return values are covered. Description still mentions stdout/stderr/return code. With one parameter fully described and prerequisites noted, the description is complete for this tool's complexity.

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?

Input schema has 0% coverage (no description), but the description compensates by explaining the single parameter 'example_name' with concrete examples (pam_example, lam_example), adding meaning beyond the schema's title.

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 'Execute a JACTUS example and return its output' with specific details on output (stdout, stderr, return code). Distinguishes from sibling jactus_get_example by mentioning jactus_list_examples to see available examples.

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?

Provides clear context: use to run an example, mentions timeout, environment variable requirement, and references jactus_list_examples for availability. Lacks explicit 'when not to use' but sufficiently guides usage.

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