jactus_list_examples

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

With no annotations, description carries full burden. Discloses it lists examples from a specific directory and notes the prerequisite. Implicitly read-only. Could add details on error behavior (e.g., if directory missing), but sufficient for basic usage.

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?

Three sentences plus a note — every sentence adds value. Front-loaded with main action. No wordiness.

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 0-parameter list tool with output schema present, description adequately covers purpose, returns, and prerequisites. No gaps given low 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?

No parameters exist (input schema empty), so baseline is 4. Description does not need to add parameter details; it correctly states it lists all examples with no filters.

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 it lists all available code examples in JACTUS, specifies return type (Python scripts and Jupyter notebooks), and distinguishes from sibling tools like jactus_get_example and jactus_run_example by mentioning them as retrieval/execution alternatives.

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 usage context (listing examples) and a prerequisite note (JACTUS source tree access and env var). Lacks explicit when-not-to-use or alternatives beyond get/run, but adequate for a simple list tool.

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