gerent365_delete_job_position

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

There are no annotations, so the burden falls on the description. It does not disclose that deletion is permanent, whether associated records are affected, or any permission requirements. The only behavioral detail is the action itself.

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 a single, front-loaded sentence that directly states the action and scope. It is concise and free of unnecessary words, scoring highly for structure.

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?

Given the simplicity of a one-parameter delete, the description is functionally adequate but lacks any mention of side effects or return value. For a destructive operation with no annotations, it would benefit from cautionary context.

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 schema already documents the 'id' parameter with its description, so the description's mention of 'ID' adds no new information. Since schema coverage is 100%, a baseline score of 3 is appropriate, though no additional semantic detail is provided.

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 uses a specific verb 'Elimina' (delete) and identifies the resource 'puesto de trabajo' (job position) with the method 'por su ID' (by its ID), making it distinctly the deletion tool among siblings like create/update/list job positions.

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?

No usage context is provided; it simply states the deletion action and the ID parameter. There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions.

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