assets-get-spine-skeleton-info

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

No annotations are provided, so the description carries the full burden. It discloses the requirement for an atlas key and the type of info returned (animations, skins). However, it does not mention error behavior, what happens if the key is invalid, or the exact output structure. This is adequate for a simple read operation but could be more explicit.

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?

Three sentences, all essential. The purpose is front-loaded, and each sentence adds unique value without redundancy. Perfectly concise for the information conveyed.

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?

No output schema exists, so the description should clarify the return value. It mentions 'animations and skins' but does not specify the exact data structure or format. For a tool with 2 simple params, this is minimally adequate but leaves the agent guessing about output details.

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%, but the description adds valuable context beyond the schema: it explains the relationship between dataKey and atlasKey, and provides a common usage pattern (preview key). This helps the agent understand the semantics and typical workflow.

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 tool retrieves skeleton info (animations and skins) for a given Spine skeleton key. The verb 'Get' and resource 'skeleton info' are specific, and the description distinguishes from sibling tools by focusing on info retrieval rather than listing or other operations.

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 explains that building the skeleton info requires an atlas key, suggests using a 'preview' atlas key if available, and advises asking the user otherwise. This provides clear context for when and how to use the tool, though it lacks explicit 'when not to use' guidance.

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