Get current moveset

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds what is aggregated (saved index/hash from tree.ehehetilde, last switch pick, resolved name), which is real context beyond the annotations. It does not describe the response shape or what happens when no moveset is saved, leaving a moderate gap.

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?

A single efficient sentence with no padding. It is front-loaded on the primary output. The internal jargon ('tree.ehehetilde') reduces readability slightly but costs no length.

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?

With no parameters, no output schema, and read-only annotations, the burden is light. The description does name the components returned, which is helpful, but the opaque 'tree.ehehetilde' reference and the absence of any note on empty/unsaved state leave it only adequately 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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to document here, and it does not confuse the picture.

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?

States a specific verb (Show) and a specific resource (saved MovesetIndex/MovesetHash, last switch_moveset pick, resolved name). It is a clear 'get current state' tool distinguishable from reanim_switch_moveset by the read-only framing. It does not explicitly distinguish itself from the parallel reanim_get_current_dance or reanim_check_movesets sibling, so it stops short of a 5.

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 guidance on when to use this versus reanim_check_movesets, reanim_list_movesets, or reanim_switch_moveset. The mention of 'last MCP switch_moveset pick' implies a relationship to that sibling but never states the condition for choosing this tool. Usage must be inferred entirely from the name.

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