art.pipeline.analyze

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

With no annotations, the description carries the burden of behavioral disclosure. It is good that the description names the returned analysis categories and clarifies that the reference must already be uploaded. However, it is silent on side effects, required versus optional parameters, and what happens when both file_path and reference_id are supplied.

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 focused sentences with no filler. It front-loads the action and return kinds, then states the input requirement. Every sentence earns its place.

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?

The description is adequate for invoking the tool with file_path or reference_id and provides a basic sense of outputs despite the lack of an output schema. However, four of the six parameters (pose, facing, subject, category) are unmotivated in the prose, and there is no guidance on how this tool fits among the many pipeline and analysis-related siblings.

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?

The input schema already documents all six parameters, so the baseline is 3. The description adds real value by expressing the either/or relationship between file_path and reference_id and adding the 'already-uploaded' precondition, which are insights not present in 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 names a specific action ('Analyze a reference image') and lists meaningful outputs ('palette, silhouette, composition, pixel characteristics'), so an agent can tell what the tool does. It does not explicitly contrast itself with similar-sounding siblings like art.canvas.analyze_ref or art.pipeline.* tools, so it stops just short of a 5.

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 description gives no guidance about when to use this tool versus the many sibling alternatives. It only provides the file_path-or-reference_id input choice, which is helpful for calling the tool but does not help an agent decide whether this tool is the right one.

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