art

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose real constraints: execute/batch only start selected native apps, explicit save/export is required, and there is no automatic live GUI control. What is missing is side-effect, permission, and state-persistence detail for a tool that can launch applications.

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 text is a run of telegraphic, semicolon-separated fragments with no subject in most clauses, front-loaded with the least informative sentence ('One ArtCraft entry'). Density is high but readability is low; the ordering does not help an agent parse the routing rules.

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-operation dispatcher with a nested arguments object, 0% parameter coverage, no annotations, and no output schema, yet the description never enumerates the operations or explains the argument structure. It omits doctor, refresh, and control entirely, leaving an agent unable to call most of the surface 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 0%, so the description must compensate and largely does not. It mentions a handful of the 11 enum values (catalog, guide, search, describe, execute, batch, native, rpc) but never defines any of them, and the generic nested 'arguments' object is not explained at all despite being where operation-specific payloads must go.

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 tool name 'art' is opaque and the opening line 'One ArtCraft entry' largely restates it, but the following sentences hint at the real function: a single gateway exposing catalog/search/describe/execute/batch/native/rpc operations. There is no explicit verb+resource statement such as 'invoke ArtCraft native app operations', so the agent must infer the purpose from the operation hints rather than read it.

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?

It does prescribe a workflow: start with catalog/guide, then search and describe to get native schemas, and use execute/batch only for selected native apps. It also routes raw vendor CLI through native and resources/prompts through rpc. However, operations like doctor, refresh, and control get no guidance, and there are no explicit when-not-use conditions.

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