get_sprite_info

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

No annotations provided, so description carries full burden. It discloses that the tool is read-only ('get info') and lists the output fields, providing clear behavioral expectation. Could mention error conditions (e.g., sprite not found) but not necessary for a simple read 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?

The description is a single sentence that immediately states purpose and lists key info. No extraneous words, highly efficient.

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 simple complexity and full schema coverage, the description adequately lists output fields. It lacks mention of error handling or return structure, but for a straightforward read tool this is nearly complete.

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 both parameters described (projectDir and spriteName). The description adds no additional meaning beyond the schema; it lists output fields but does not elaborate on parameters themselves. Baseline of 3 is appropriate.

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 'Get detailed info about an existing sprite' and lists specific attributes (dimensions, frame count, origin, collision settings). This verb-resource pair is precise and distinguishes from sibling tools like get_object_info or get_room_info.

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 implies when to use (when needing sprite info) but provides no explicit guidance on when not to use or alternatives. Sibling tools like edit_sprite or list_resources exist but are not mentioned.

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