Create A Copy Of The Action Plan Template Item In The Item'S Section.

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

Discloses HTTP 201 success and that it creates a new object. Annotations already indicate it's a write operation (readOnlyHint=false). No added context about side effects, permissions, or error handling beyond the basics.

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?

Four sentences covering purpose, usage hint, required parameters, and API endpoint. Well-organized but could be more concise; every sentence earns its place.

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?

Adequate for a simple creation tool with two parameters and no output schema. Mentions the endpoint and HTTP method, but lacks details on the return object structure or potential errors.

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 coverage is 100% with descriptions. The description adds value by specifying that 'project_id' is a URL path parameter and 'plan_template_item_id' is a request body field, clarifying parameter location beyond the schema.

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?

Clearly states it creates a copy of an Action Plan Template Item and returns the created object. Slight ambiguity in phrasing 'create a new Action Plans' (plural), but overall verb and resource are clear.

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?

Explicitly says 'Use this to create a new Action Plans in Procore', but does not specify when not to use or differentiate from siblings like 'create_a_copy_of_the_action_plan_item_in_the_items_section'. No alternative tools mentioned.

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