artscii

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

No annotations provided, so description carries full burden. While 'Get' implies a read operation, the description omits error handling (what happens if ID is invalid?), caching behavior, or whether the art is returned as a string or object.

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?

Extremely efficient four-word description. Front-loaded with verb, zero redundancy, and appropriately sized for a single-parameter retrieval operation.

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?

Adequate for a simple retrieval tool with no output schema, but misses opportunity to describe the return value (the ASCII art string) or error conditions. Meets minimum viability but lacks richness expected when no annotations guide behavior.

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 has 100% coverage with examples ('cat', 'sun', 'heart'). Description acknowledges the ID parameter ('by ID') but adds no semantic context beyond what the schema already provides. Baseline 3 appropriate given comprehensive 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?

Clear verb (Get) + resource (ASCII art) + scope (by ID). However, lacks explicit differentiation from siblings like 'search' or 'list' that could also retrieve art.

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?

Provides no guidance on when to use this vs. alternatives like 'search', 'list', or 'random'. Does not mention prerequisites such as needing to know the specific ID beforehand.

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