line_art_prompt

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 discloses one useful trait — that a negative prompt is generated alongside the main prompt — but says nothing about whether an external AI is invoked, determinism, cost, or failure modes, which matters for a prompt-generation 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?

One front-loaded sentence with zero padding, which is structurally clean. However, it is under-sized for a five-parameter tool, so brevity here is more omission than efficiency.

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 no annotations, no output schema, and 0% schema description coverage across five parameters, the description is expected to compensate heavily and instead supplies a single sentence. An agent could not reliably populate 'style', 'composition', or 'line_weight' semantics from it.

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?

Five parameters with 0% schema description coverage, and the description mentions none of them. It never explains 'subject', 'style', 'composition', the 'line_weight' enum values, or what 'extra' accepts, leaving the agent to infer all input semantics from bare names.

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?

States a specific verb ('Write') and resource ('line-art prompt ... for an AI tattoo generator'), so the agent knows what is produced. It does not explicitly distinguish itself from siblings build_tattoo_brief or check_small_size_legibility, but the resource is distinct enough to infer separation.

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling tools or when one should be preferred over another. The agent must guess whether this replaces or complements build_tattoo_brief.

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