Create Meeting

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

Annotations show readOnlyHint false and destructiveHint false, indicating a write operation. The description adds value by specifying that the request must use multipart/form-data for attachments and returns HTTP 201 on success. This goes beyond what annotations provide.

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 mostly concise but includes some repetition ('Create a new Meeting' and 'Creates a new Meetings') and extraneous details like the Procore API path. The key information is 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?

The description covers purpose, required parameters, attachment upload method, and success response. There is no output schema, but the description mentions the return of the created object. It does not explain error handling or the meeting object structure, but that is acceptable for a create tool with schema coverage.

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% with descriptions for all three parameters. The description restates required parameters and the multipart requirement for attachments, but does not add substantial new meaning beyond the schema. Baseline of 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 verb 'Create' and the resource 'Meeting', and explicitly says 'Use this to create a new Meetings in Procore.' It distinguishes from sibling tools like create_meeting_attendee_record and update_meeting_v1_0 by focusing on creating a top-level meeting.

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 Meetings in Procore,' which implies the primary use case. However, it does not mention when not to use it or provide alternatives for related actions (e.g., creating meeting topics or categories). The guidance is clear but lacks exclusions.

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