Create Communication Tag

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

Annotations indicate this is a write operation (readOnlyHint=false) and the description confirms it creates an object and returns it with HTTP 201. No additional behavioral details (e.g., permissions, rate limits, side effects) are provided beyond the basic creation behavior.

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; the first is clear, but the second and third contain redundant or confusing content (e.g., 'create a new Emails' and repeated schema info). It could be more concise and focused.

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 the tool's simplicity (2 params, no output schema), the description provides adequate context but fails to explain the concept of a communication tag or any edge cases. The confusion around emails reduces 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?

The input schema has 100% coverage, so baseline is 3. The description merely repeats required parameters from the schema without adding any semantic context about what a communication tag is or how the title is used.

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 states the tool creates a communication tag on a project, which is clear. However, it then says 'Use this to create a new Emails in Procore' and 'Creates a new Emails', confusing the resource type and potentially misleading the agent. The purpose is stated but muddled by incorrect references to emails.

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 mentions required parameters but provides no guidance on when to use this tool versus alternatives (e.g., create_email or create_communication_thread). It does not specify when not to use it or what distinguishes it from sibling tools.

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