reorder_project

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a mutation operation ('move') but does not detail side effects, permissions, or error conditions. The output schema exists, but the description does not reference it, leaving some behavioral aspects implicit.

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 two sentences plus a bullet list, with no redundant information. The first sentence states the purpose clearly, and the list explains parameters and constraints efficiently.

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 description covers the main functionality and parameter constraints. It implicitly assumes the 'same folder' context (stated) but does not clarify ordering semantics or error handling. Given the simple nature and existence of an output schema, it is mostly 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 schema has 0% description coverage, so the description fully compensates. It lists all three parameters and explains the constraint that exactly one of 'before_project_id' or 'after_project_id' is required, adding crucial meaning beyond the schema names and types.

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 tool moves a project relative to another project within the same folder. It uses specific verbs ('move') and resource ('project'), and distinguishes from the sibling tool 'reorder_task' which operates on tasks.

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 specifies that exactly one of 'before_project_id' or 'after_project_id' is required, but does not provide guidance on when to use this tool versus other project management tools like 'update_projects' or 'delete_projects'. It implies the context of reordering but lacks explicit alternatives or exclusions.

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