Spine export

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 only describes the high-level function without disclosing behavioral traits such as side effects (e.g., file creation/modification), required permissions, rate limits, or error conditions. This leaves the agent without essential context for safe invocation.

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, well-structured sentence of 20 words. It is front-loaded with the verb 'Export' and immediately conveys the core functionality. No redundant or extraneous information is present.

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 tool has 7 parameters, no output schema, and no annotations, the description is too brief. It does not explain the export process, how parameters interact (e.g., overrides), or what the output is. The agent lacks sufficient context to use this tool effectively in complex workflows.

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?

With 71% schema description coverage, the baseline is 3. The description adds minimal value beyond the schema, essentially reiterating that exportSettings can be a JSON file path or default modes. Other parameters like clean, inputPath, and outputPath are not elaborated in the description.

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 action ('Export'), the resource ('Spine project or data file'), and the method ('with export settings JSON file or default json/binary mode'). It effectively distinguishes this tool from sibling tools like spine_pack or spine_summarize_atlas, which handle different 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 implies the tool is for exporting Spine data, but it does not explicitly state when to use it versus alternatives like spine_pack for packing or spine_cli_info for information. No guidance on when not to use or prerequisites is provided.

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