Create Environmental

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

Annotations (readOnlyHint=false, destructiveHint=false) are consistent with creation. The description adds that it returns HTTP 201 and the created object, which is useful. However, it does not disclose potential side effects, authorization requirements, or failure modes beyond the schema.

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 relatively concise but contains redundancy: 'Creates an Environmental record' and 'Use this to create a new Incidents in Procore' essentially say the same thing. The typo ('Incidents' instead of 'Environmental record') also reduces clarity.

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 11 parameters and no output schema, the description should provide more context on return values, error responses, or usage scope. It only mentions required params and the endpoint, leaving gaps for an AI to understand the full tool behavior.

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 description coverage is 100%, so the schema already describes all parameters. The description only repeats required parameters (already in schema) and adds no new meaning or context for the parameters beyond what's in the input schema.

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 an Environmental record and uses a verb+resource structure. However, there is a typo: 'new Incidents' instead of 'Environmental record', which could cause confusion with the create_incident tool. It distinguishes from siblings like list_environmentals or destroy_environmental.

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 Incidents in Procore' but provides no guidance on when to use this tool vs alternatives like create_incident or update_environmental. No when-not-to-use or contextual hints beyond a basic purpose statement.

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