Create Delivery Log

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

Annotations are present (readOnlyHint=false, destructiveHint=false) and description adds that it returns the created object on success (HTTP 201) and mentions required parameters. No contradiction. Describes the action and result well.

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?

Two concise sentences with structured info at the end. Redundancy in mentioning 'Daily Log records' twice but overall efficient and front-loaded with main purpose.

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 100% schema coverage, no output schema, and annotations, the description covers purpose, required params, return behavior, and API endpoint. Could mention output structure but not critical for a create 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?

Schema coverage is 100%. Description mentions required parameters (project_id, delivery_log) and adds that project_id is a URL path parameter and delivery_log is a JSON body, but does not elaborate beyond schema. Baseline score 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 it 'Creates single Delivery Log in the specified Project' and specifies the context 'Procore' and 'Daily Log records'. It distinguishes itself from siblings by focusing on delivery logs, and includes HTTP 201 return info.

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?

Provides context for usage ('Use this to create a new Daily Log records in Procore') and lists required parameters, but no explicit when-not-to-use or alternative tools. The API endpoint is given, but not guidance on when to choose this over other logs.

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