Bulk Create Plan Template References

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

Description adds value beyond annotations by noting partial failures and HTTP 201 response. Annotations (readOnlyHint=false, destructiveHint=false) are consistent; the description clarifies the write operation and error handling.

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?

Description is informative but slightly verbose, including endpoint path and Procore API reference. Could be trimmed to essential lines, but still well-structured and readable.

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?

Given 3 parameters, no output schema, and minimal annotations, the description adequately covers purpose, required fields, partial failure behavior, and API context. Agent has enough to decide and invoke correctly.

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% and descriptions in schema already explain parameters. Description adds no additional semantic insight beyond repeating required parameter names ('company_id, plan_template_references').

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?

Description clearly states the verb 'create' and resource 'plan template references', distinguishing it from sibling bulk_create tools (e.g., bulk_create_action_plan_template_references) by specifying 'Action Plans records' and the endpoint path.

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 many Action Plans records in a single request' and warns about partial failures. However, it does not explicitly list when not to use it or alternatives among the many bulk_create siblings.

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