get_sprite_info

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

No annotations provided. Description only lists output, not behavior (read-only, side effects, permissions, rate limits). With no annotations, description must cover behavioral traits but fails to do so.

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?

Single sentence is concise and front-loaded with purpose. Structure could be improved by breaking into bullets or adding examples, but currently efficient and clear.

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?

Lists output fields adequately but omits error cases, required state (sprite must be loaded?), units of size, or color mode options. With no output schema, description should be more thorough.

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?

Only parameter 'filename' has 0% schema description coverage. Description adds no extra meaning (format, allowed values, path conventions). Should compensate for missing schema metadata.

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 uses specific verb 'Return' and lists exact data returned (size, colour mode, frames, layer tree, tags, palette). It clearly distinguishes from siblings that return individual pieces like get_palette or get_pixels.

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 guidance on when to use this comprehensive tool vs specific getters like get_palette or get_tilemap. Implies it's for overall sprite info but doesn't state when to prefer this over alternatives.

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