Create Daily Construction Report Log

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

Annotations provide basic read/destructive hints. The description adds that success returns HTTP 201 and the created object. It does not disclose additional behaviors like permission requirements or what happens on duplicate submission, but does not contradict annotations.

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 four sentences, front-loaded with the purpose, and includes essential details (return value, required params, endpoint) without unnecessary words.

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?

No output schema exists, so the description should explain return value more thoroughly. It mentions the created object but not its structure. Also, given many sibling log tools, a reference to when this specific log is appropriate could improve completeness.

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?

Input schema has 100% coverage with descriptions. The description highlights required parameters but adds little extra meaning beyond the schema. The attachments parameter has a truncated schema note but description does not elaborate.

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 'Creates single Daily Construction Report Log' and specifies the API endpoint and context ('Project Management > Daily Log'). It distinguishes from sibling log tools by naming the specific log type.

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 tells the agent to use this tool 'to create a new Daily Log records in Procore' and lists required parameters. However, it does not explicitly state when not to use it or provide alternatives like other log creation tools.

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