Delete A Time Off Record

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

Annotations already indicate destructive and readOnly=false, but the description adds substantial context: permanent deletion, irreversibility, repeat call returns 404, typical HTTP error statuses (401/403/404), company_id default behavior, and the endpoint. This goes well beyond annotations and fully discloses the tool's 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 longer than average, but every sentence carries useful information: purpose, prerequisites, return value, permanence, error handling, and endpoint. It is well-structured and front-loaded with the core action, with 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?

For a destructive tool with no output schema, the description covers all essential aspects: what is deleted, return value, prerequisites, default parameter behavior, failure modes, and the exact API endpoint. This gives the agent complete information to invoke the tool correctly and anticipate outcomes.

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 already describes all three parameters (100% coverage). The description adds value by explaining company_id can default to config value when omitted, and that person_id and time_off_id must reference existing records. This enhances the schema's basic 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 a Time Off record for a specific Person within a company, and specifies the returned ID. It is distinct from sibling time-off tools like create, get, and update by using the verb 'Deletes' and emphasizing permanent removal.

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 explicit usage guidance: confirm the target ID with a show/list tool before calling, and resolve person_id/time_off_id with the matching list tool first. It also explains company_id defaults to procore_set_config, giving clear context for when to invoke the tool, though it does not explicitly name alternative tools.

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