Delete Instruction

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

The description adds significant context beyond the annotations, including the permanent nature of the deletion, the 404 on repeat calls, and common error status codes (401, 403, 404). These details are not in the annotations and are valuable for an agent to understand the tool's behavior. No contradiction with annotations is present.

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 reasonably concise but contains redundancy, particularly the repeated instruction to resolve the id with the matching list tool. The first sentence and error-handling sections are well-structured, but the duplication could be removed to improve conciseness.

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 delete tool, the description covers purpose, preconditions, permanent behavior, error handling, and parameter defaults. No output schema exists, so explaining return values is unnecessary. This is a comprehensive description that leaves little ambiguity.

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%, and the description adds meaning by explaining that project_id defaults to the configured value and that id must identify an existing parent record resolved via a list tool. This provides practical semantics beyond the schema's simple URL path parameter descriptions.

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 deletes the specified Instruction, using a specific verb and resource. It distinguishes it from similar tools by referencing the Daily Log context and the exact endpoint, making the purpose unambiguous.

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 explicitly instructs the agent to confirm the target id with the matching show or list tool before calling, which is essential for a delete operation. It also provides context about project_id defaulting from procore_set_config. It doesn't name a specific sibling tool but offers clear preconditions.

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