art.provider.fallback

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

No annotations are provided, so the description carries the full burden. It does disclose the core fallback trait, but it does not explain what counts as a failure, whether the operation is destructive, what happens on total failure, how dry_run behaves, or what the response looks like. Significant behavioral context is missing.

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?

A single front-loaded sentence with no filler. It communicates the primary behavior immediately and earns its place; nothing extraneous is present.

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?

This is an 11-parameter tool with nested objects, no output schema, and no annotations. The one-sentence description is far from sufficient: it omits operation semantics, output handling, timeout behavior, references, asset context, and return value expectations. Agents would likely need substantial trial and error or external documentation to use this correctly.

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 only 18%, so the description must compensate, but it does not. It repeats the provider/fallback role already described in the schema and adds no meaning for the other nine parameters such as operation, style, output, dry_run, timeout_seconds, or references. Agents cannot infer how to construct a valid call from this description.

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 a specific verb ('Execute') and resource ('art operation') and immediately communicates the defining behavior: try primary provider, fall back to a secondary. This distinguishes it from siblings like art.provider.execute, though 'art operation' remains somewhat generic and no sibling is explicitly contrasted.

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 fallback behavior implies the tool is for cases where resilience or redundancy is needed, so usage context is suggested rather than stated. There is no explicit when-to-use guidance, no named alternative, and no exclusion such as 'use art.provider.execute when fallback is not required.'

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