Create Sub Job

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

The description notes that success returns HTTP 201 and the created object, adding behavioral insight beyond annotations (which only indicate non-readOnly, non-destructive). No contradictions with annotations, but could disclose 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?

The description is three sentences, efficient but slightly redundant with 'Work Breakdown Structure records' appearing twice. Generally well-structured and front-loaded.

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?

Lacks explanation of what a Sub Job or Work Breakdown Structure is, which may confuse agents unfamiliar with Procore. No output schema, but description partially addresses success. Adequate for a straightforward creation tool.

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?

With 100% schema coverage, the description adds little beyond repeating required parameters (project_id, sub_job). It does not explain the substructure of the sub_job object, which has additionalProperties: true. 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 new Sub Job, specifically Work Breakdown Structure records in Procore, using the verb 'Create'. It distinguishes from sibling tools like list_sub_jobs and delete_sub_job.

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 Work Breakdown Structure records' but provides no guidance on when not to use this tool or alternatives among the many create tools. Lacks explicit usage context.

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