Create Company Action Plan Template Item

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

Annotations indicate non-read-only and non-destructive. The description adds that it creates and returns the object on HTTP 201, plus mentions the endpoint. It does not disclose side effects, error handling, or constraints beyond the schema. Acceptable but not rich.

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 concise (4 sentences), front-loaded with purpose and key info (required params, endpoint). Minor redundancy (repeats 'Action Plans') but overall efficient.

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?

For a create tool with 5 parameters and no output schema, the description covers return value (HTTP 201), required params, and API location. It lacks explanation of optional parameters (description, holding_type) but schema fills that gap. Generally 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?

All 5 parameters have schema descriptions (100% coverage), so the schema already explains them fully. The description only lists required parameters but does not add meaning beyond the schema. Baseline 3 is appropriate.

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 creates a Company Action Plan Template Item, with specific verb and resource. It mentions required parameters and the HTTP 201 response. However, it does not explicitly differentiate from sibling tools like create_company_action_plan_template_item_assignee, but the purpose is 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?

The description says 'Use this to create a new Action Plans in Procore' and lists required parameters, providing clear context for when to use. However, it offers no guidance on when not to use or alternatives, such as when to use other create tools for related entities.

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