Move Action Plan Back Into "Draft"

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

The description says it removes signatures and sets status to draft, but also states 'Creates a new Action Plans' (HTTP 201), which is contradictory to 'moving back'—it suggests creation rather than modification. Annotations give no behavioral details, so the description carries the burden but introduces confusion.

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 includes multiple sentences with some redundancy (e.g., 'Use this to perform the move action action') and extra API info (Procore API, endpoint). Not excessively long but not front-loaded; each sentence earns its place, but conciseness could be improved.

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?

No output schema, so description should explain return value—it does ('returns the created object'). Missing permission requirements, error conditions, and whether the plan is cloned or modified. Adequate for a simple action but not fully 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 covers both parameters with descriptions (100% coverage). The description only lists them as required without adding meaning beyond the schema. Baseline 3 applies.

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 it moves an action plan back to 'Draft', removing signatures and setting status to draft. It specifies the verb 'move', the resource 'Action Plan', and the target state, distinguishing it from siblings like 'move_action_plan_into_in_progress'.

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 indicates use when needing to revert an action plan to draft for updates. It says 'Use this to perform the move action action on Action Plans' and notes 'Once in this state, the Plan is able to be updated.' It lacks explicit when-not-to-use or alternatives, but context is clear.

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