Check the export in Unity

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

readOnlyHint=true already tells the agent this is a safe read-like operation, and the description adds useful context beyond that: the work happens in a throwaway project, runs about 30 seconds, and reports per-bone animation deltas plus CPU/GC metrics. It still omits what a failing run looks like, whether Unity must be installed, and whether anything is written to disk despite the readOnly annotation.

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?

It is a single front-loaded sentence with no filler, which is good. But the telegraphic style ('perf: CPU/GC per skeleton', 'fresh export ... bone by bone') trades clarity for brevity, and the trailing doc-anchor sentence is a fragment rather than usable guidance.

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?

For a tool with 22 parameters including nested objects, four enums, and no output schema, the description is markedly under-specified. An agent would not know how to configure render, compression, or mecanim checks, nor what results to expect, without following the external link.

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 22 parameters and only 32% schema description coverage, the description must carry weight, but it mentions only 'perf' in passing and defers the rest to an external doc link. High-impact options like renderPipeline, batching, compression, mecanimTransitions, and tracksPhysics are undocumented in both places, so an agent cannot tell what they change.

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 names a concrete action and object: fresh export into a throwaway Unity project, with every animation compared bone by bone against spine-core, plus CPU/GC perf per skeleton. That is far more specific than the title 'Check the export in Unity'. It does not, however, distinguish itself from related siblings such as spine_unity_import or spine_validate, leaving the agent to infer the boundary.

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?

There is no statement of when to choose this over spine_unity_import, spine_validate, or spine_web_check, and no prerequisites (e.g. which Unity versions are available). The only pointer is a doc anchor, 'docs/USAGE.md#into-your-unity-project', which outsources the guidance rather than providing it.

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