Create Instruction Types

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate a write operation, which the description confirms with 'Creates'. The description adds that it returns the created object on HTTP 201, but no further behavioral details (e.g., permissions, side effects) are provided. With annotations present, this is adequate but minimal.

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 three sentences: purpose, usage context, required parameters and API details. It is front-loaded and efficient, though the phrase 'Creates a new Daily Log records' is slightly redundant.

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?

For a simple create tool with full schema coverage and annotations, the description adequately covers what the tool does, its context (Daily Log), and required parameters. It could mention uniqueness constraints or response structure, but it is reasonably complete.

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?

Both parameters are fully described in the input schema (100% coverage). The description merely restates that project_id and name are required, adding no new semantic meaning beyond what the schema already provides.

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 tool creates a new Instruction Type associated with a project, using specific verbs and resources. It distinguishes from sibling tools by focusing on creation, though it does not explicitly differentiate from other create tools like 'create_instructions'.

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 provides context for use ('Use this to create a new Daily Log records in Procore'), implying it is for Daily Log management. However, it offers no guidance on when not to use it or alternatives (e.g., updating or listing instruction types).

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