Reorder tools/steps in a project
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| tool_orders | Yes | Array of tool IDs and their new step orders | |
| project_slug | Yes | The slug of the project to reorder tools in |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Reorder' implies mutation but does not state whether the operation replaces the entire order, accepts partial updates, or what side effects occur. It also does not mention permissions or response behavior.
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, front-loaded sentence with no filler. It is appropriately concise for a tool whose schema handles parameter details, though it could benefit from a bit more context without becoming verbose.
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 tool has no annotations, no output schema, and a minimal description. Given the complexity of reordering multiple steps, the description fails to explain key behaviors like whether the order is fully replaced or merged, or what the return value looks like. The schema covers parameters but not the operation's overall effect.
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 100%, so the schema already documents all parameters (session_id, project_slug, tool_orders). The description adds no further semantic meaning beyond the schema, hence the baseline score of 3.
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 action ('Reorder') and the resource ('tools/steps in a project'), which distinguishes it from sibling tools like update_tool or toggle_tool. The verb and scope are specific and unambiguous.
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 guidance on when to use this tool versus alternatives. The description only states what it does, not the context or conditions for using it. No exclusions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, targeting specific resources (projects, data sources, tools) and actions (add, create, delete, update). Slight overlap exists between toggle_tool and update_tool, and between add_data_source and add_tool, but descriptions clarify the differences.
All tool names follow a consistent verb_noun pattern with snake_case, such as add_data_source, create_project, delete_tool, and reorder_steps. No mixing of conventions or vague verbs.
13 tools is within the ideal range for a project management server. Each tool serves a clear purpose in managing projects, data sources, tools, and sessions, without unnecessary redundancy.
Core CRUD operations are covered for projects and tools, with additional operations like reorder and toggle. Minor gaps exist: data sources lack an update operation, and there's no explicit list/get for tools or data sources, but project details likely cover this.
