artscii

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'with metadata' which hints at return content, but fails to disclose critical behavioral traits like pagination, result limits, or caching behavior for what could be a large dataset ('all available').

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, efficient sentence of six words. It is front-loaded with the action verb and contains no redundant or wasteful text. Every word 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?

Given the lack of output schema and annotations, the description is insufficient for a complete understanding. While it mentions 'metadata,' it does not describe the return structure, format, or whether the result is an array or object. For a tool returning 'all' items, pagination details should be included.

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 has zero parameters. According to scoring guidelines, 0 parameters establishes a baseline score of 4. No parameter description is needed or provided.

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 the verb (List) and resource (ASCII arts) and adds scope detail ('all available'). However, it does not explicitly differentiate from siblings like 'search' or 'get' in the text, though the tool name helps imply unfiltered enumeration.

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 guidance is provided on when to use this tool versus alternatives like 'search' (for filtering) or 'get' (for specific items). The description does not mention prerequisites, rate limits, or pagination concerns for retrieving 'all' items.

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