Delete A Job Title

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

Beyond annotations, the description discloses critical behavioral traits: 'Permanently removes the job title. This cannot be undone, and a repeat call returns 404.' It also details error payload scenarios (401, 403, 404) and the company_id default, providing substantial context beyond the structured annotations.

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 dense but every sentence adds value: action, preconditions, defaults, permanence, error handling, required parameters, and API endpoint. It is well-structured and front-loaded with the core purpose. No wasted words.

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 the action, prerequisites, defaults, error responses, and API endpoint thoroughly. It does not explicitly state the success response (e.g., 204 No Content), which is a minor gap given there is no output schema. Overall, it is nearly complete for a delete tool.

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%, so the baseline is 3. The description adds meaningful parameter context: company_id defaults to the procore_set_config value when omitted, and job_title_id must refer to an existing parent record. This enhances semantic understanding beyond the 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 the tool's action: 'Deletes a Job Title given a company ID and job title ID.' It uses specific verb+resource and even provides the endpoint, making the purpose unambiguous. It also distinguishes from sibling list/show tools by instructing to confirm the id with them.

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?

Explicit guidance is provided: 'Confirm the target id with the matching show or list tool before calling' and 'job_title_id must identify an existing parent record — resolve it with the matching list tool first.' It also explains the company_id default behavior and common failure cases, which tells the agent when and how to use the tool correctly.

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