get

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

With no annotations provided, the description carries the full burden. It discloses the return type ('scaled pixel art PNG') and implies a read-only operation via 'Returns', but does not mention error behavior or any side effects. For a simple retrieval tool, this is adequate but not rich.

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 short sentences, front-loaded with the core purpose and a brief return format. Every word contributes; no filler.

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 tool is simple with well-documented parameters and a clear return format stated in the description. However, there is no output schema and no mention of error cases, so an agent might wonder what happens if the ID is not found. Overall, it is complete for a straightforward retrieval tool.

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 coverage is 100% with detailed descriptions for all three parameters, including examples, defaults, and constraints. The description adds no new parameter semantics beyond restating that the sprite is retrieved by ID and returns a scaled PNG.

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 states a specific verb ('Get') and resource ('sprite as a PNG image by its ID'), clearly distinguishing it from sibling tools like mirror, search, or export. The mention of 'by its ID' clarifies the retrieval method.

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 explicit when-to-use or alternatives are stated. The description implies this is the tool for fetching a sprite by ID, and the schema's mention of 'Use search' provides a hint for palette discovery, but there is no direct guidance on when not to use this tool or when to prefer a sibling like inspect.

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