raw_track_move_bottom

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It warns that the command 'may open a dialog or change project state' and advises inspecting the command name first, which is useful caveat information for an agent deciding whether to invoke it.

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 concise and front-loads the core purpose in the first sentence. The remaining clauses add behavioral caveats without excessive padding, though 'TrackMoveBottom:' slightly duplicates the tool name and the final advisory is a bit vague.

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 parameterless action with no output schema, the description covers what the command does, its no-argument nature, and potential side effects/dialog risk. It is sufficient for basic invocation, though it could more explicitly define what 'inspect the command name first' entails.

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 has zero parameters and the schema is an empty object, so there is nothing to document. The description reinforces this by explicitly stating 'no-argument,' which supports correct invocation.

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 a specific verb and resource: 'Move the focused track to the bottom.' It clearly distinguishes itself from sibling tools like raw_track_move_top, raw_track_move_up, and raw_track_move_down, which involve different movement directions.

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 does not explain when to use this tool versus alternatives such as raw_track_move_top or raw_track_move_up. It labels the action as static and no-argument, but offers no context about choosing this command or what makes it preferable over other track movement tools.

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