action_run

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

With no annotations provided, the description carries the burden of behavioral disclosure and does add useful detail: it checks scope first and reports failures as window-scoped, a dead registry entry, or a typo. However, it does not disclose potential side effects of running arbitrary action chains or what a successful run returns, which is a meaningful gap for such a powerful tool.

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 two sentences with the core purpose front-loaded and the failure-diagnosis detail compactly included in the second. There is no filler, redundancy, or unnecessary structure.

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?

All parameters are documented and the description provides valuable failure diagnostics, but there is no output schema and no statement about return values or destructive side effects. For a tool that can run arbitrary action chains, a note about what happens on success or about file mutation would make it fully complete.

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 description coverage is 100%, so every parameter is already documented in the schema. The description adds some context by explaining the scope check that relates to `ignore_scope` and the failure categories, but it does not add significant parameter-level semantics beyond the schema.

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 states a specific verb and resource: 'Run any raw Inkscape action chain.' This clearly positions it as the generic action-execution tool among more specialized siblings. It does not explicitly contrast itself with `action_find` or the higher-level helpers, so it falls just short of the top tier.

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 phrase 'any raw Inkscape action chain' implies it should be used when a raw action is needed, but the description does not explicitly say when to prefer it over dedicated tools or when not to use it. There is no mention of alternatives, leaving the agent to infer the selection logic.

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