Create Action Plan Template Approver

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

Annotations already indicate this is a non-idempotent write operation. The description adds the HTTP 201 response and endpoint, but does not disclose unexpected behaviors or side effects beyond what annotations imply.

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 contains four sentences, but includes redundancy (e.g., two sentences about creation) and a slightly misleading phrase about 'Action Plans'. It could be more concise and focused.

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 simple create tool with three parameters, the description covers the essential action and requirements. However, it lacks guidance on when to use this over bulk operations and does not clarify the return object structure (no output schema).

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 parameters are documented in the schema (100% coverage). The description merely lists required parameter names without adding semantic context, such as what a 'party_id' represents or how to obtain it.

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 creates an Action Plan Template Approver for a given Project Action Plan Template, distinguishing it from sibling bulk operations. However, it does not explicitly differentiate from the bulk_create variant.

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?

No guidance on when to use this tool versus alternatives like bulk_create. The description contains a confusing statement: 'Use this to create a new Action Plans in Procore' which mislabels the resource and does not help with decision-making.

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