Create Drawing Upload

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

Beyond annotations (which already indicate readOnlyHint=false and destructiveHint=false), the description adds that the upload processes asynchronously after the response, which is useful behavioral context.

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 somewhat verbose with redundant phrases like 'Use this to create a new Drawings in Procore. Creates a new Drawings and returns the created object on success (HTTP 201).' It could be more concise.

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?

With no output schema, the description adequately explains the return value (created object) and async behavior. It covers key parameters and points to a tutorial. However, it lacks explicit comparison to sibling tools.

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?

The schema covers 100% of parameters. The description adds context by explaining that drawing_log_imports should have one per file/upload and lists the required parameters. This goes beyond the schema's structural details.

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 that it creates a Drawing Upload in a specified project and breaks down what that includes (DrawingUpload, DrawingLogImport, ProstoreFile). However, it does not differentiate itself from sibling tools like create_drawing, which could cause confusion.

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 includes a link to a tutorial and notes that it is used to create drawings, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions.

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