run_macro

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

Adds some behavioral context beyond annotations (return value, log tail, timeout hint) but does not disclose potential mutation or side effects, given destructiveHint=false.

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?

Two sentences, each serving a distinct purpose: purpose/return and usage advice. No filler words.

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?

With an output schema and annotations, the description covers purpose and return but lacks details on side effects, prerequisites, or security considerations for arbitrary code execution.

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 covers both parameters with examples and default values; description adds no additional semantic value beyond restating macro_code as 'ImageJ1 macro text'.

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 'Execute ImageJ1 macro text in the current Fiji session' and specifies return values, effectively distinguishing from siblings like run_batch_macros and parse_macro_output.

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 guidance to prefer small, focused macros and increase timeout for heavy I/O, offering clear context for usage but not explicitly contrasting with alternative tools.

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