art.provider.execute

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it only says 'execute.' It does not state whether execution is asynchronous (the existence of art.provider.cancel hints it may be), what side effects occur (asset creation, file writes, registration), or what the dry_run parameter does. The description is not misleading, but it adds almost no behavioral context beyond the bare verb.

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 a single nine-word sentence with zero filler and the core verb front-loaded. It is well structured, though the brevity borders on under-specification for a tool of this complexity; the structure earns credit, but the length limits the information conveyed.

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 10 parameters, 0% schema coverage, no annotations, no output schema, and over 70 siblings, a one-sentence description is far from complete. Missing context includes return values, async versus sync behavior, side effects, parameter semantics for most fields, and any required setup steps. An agent would need to inspect other tools or probe to use this safely.

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 0%, so the description must compensate, but it only implicitly sheds light on provider_id and operation. The other eight parameters — including the required nested style object, output, references, asset_id, asset_type, and dry_run — receive no semantic clarification in either the schema or the description. This is a substantial gap for a 10-parameter tool.

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 names a specific verb ('execute'), a resource ('art generation operation'), and a qualifier ('via a provider'), so an agent can tell this is the run action rather than an introspection tool like art.provider.list or art.provider.capabilities. It does not, however, clarify how it differs from the similarly named sibling art.provider.operation, leaving some potential ambiguity.

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?

There is no guidance on when to use this tool versus alternatives. Given the sibling list includes closely related provider tools (art.provider.get, art.provider.capabilities, art.provider.operation, art.provider.cancel), an agent gets no hints about prerequisites such as checking capabilities first, selecting a provider, or validating a style before executing. No exclusions or alternative routing are mentioned.

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