move_list_takes

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

Annotations already state readOnlyHint=true and openWorldHint=true, so the read-only safety profile is covered. The description adds a modest behavioral detail about ordering based on sort_direction, but it does not disclose default ordering behavior, pagination characteristics, or expand semantics. No contradiction with annotations.

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 concise sentence with no filler. It front-loads the core operation ('List takes') and adds an important ordering qualifier, though it is terse enough that some behavioral and parameter details are left to the schema.

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?

The schema covers the cursor parameter and sort direction, and an output schema exists, so an agent can infer how to invoke the tool. However, the description is thin on usage guidance and leaves first/expand semantics undocumented both in the schema and description, making the overall package adequate but not 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?

Schema description coverage is only 50%, with first and expand lacking descriptions in the schema. The tool description mentions sort_direction but does not compensate for the undocumented parameters. The 'after' cursor is documented in the schema, but the description adds no semantic value for the remaining parameters.

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 specific verb and resource ('List takes') and adds an ordering behavior ('newest first when sort_direction=DESC'). It is clear enough to distinguish from move_get_take, which is singular and focused on one take, though it does not explicitly call out that distinction.

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 is given about when to use this tool versus alternatives such as move_get_take for a single take or move_create_take for creating a take. The only implied usage is the verb 'List', with no explicit when-to-use or when-not-to-use context.

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