Delete A Job Title

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

The description clearly states that the deletion is permanent and irreversible, which aligns with the destructiveHint annotation. It also specifies the resource type (Resource Planning records) beyond what annotations provide. No contradictions with 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 concise and front-loaded with the essential action. It uses four sentences to convey purpose, irreversibility, and required parameters. Minor repetition of 'This cannot be undone' reduces conciseness slightly.

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 delete operation with clear annotations and no output schema, the description sufficiently covers the tool's purpose, irreversibility, and required parameters. It is adequate for the agent to understand when and how to invoke the 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?

The input schema provides full coverage of the two required parameters (company_id, job_title_id) with descriptions. The description merely lists the required parameters without adding new semantic information, meeting the baseline expectation.

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 action ('Deletes a Job Title') and the resource ('Resource Planning records'). It distinguishes this tool from other delete tools by specifying the target resource and providing context about the Procore API endpoint. No ambiguity or tautology.

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 indicates when to use the tool: to permanently delete a Job Title. It emphasizes irreversibility, which helps the agent decide if this is the right action. However, it does not explicitly mention when not to use it or suggest alternative tools, leaving some room for improvement.

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