passgage_delete_assignment_request

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

With no annotations, the description must carry the full burden. It states the delete operation but does not disclose that deletion is permanent, whether there are side effects like cascading deletes, or any permission requirements. This is a minimal disclosure for a destructive operation.

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 sentence with no unnecessary words, making it concise and front-loaded. However, it contains a minor grammatical issue ('a assignment_request' instead of 'an assignment_request') and is slightly too terse to convey any safety or usage nuance.

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 tool with one fully described parameter, the description is technically sufficient to invoke the tool. However, the lack of annotation and absence of behavior details (e.g., permanence or error handling) leaves the agent without full context. Given the simplicity of the tool, a score of 3 seems fair.

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 covers 100% of the parameters, with the property description 'The UUID of the assignment_request to delete' already explaining the id parameter. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 'Delete a assignment_request by ID' clearly states the action (delete), the resource (assignment_request), and the identifier used (ID). This distinguishes it from sibling tools like create, update, and get assignment_request.

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 implies usage: use this tool when you need to delete an assignment_request by its ID. However, it provides no explicit guidance on prerequisites, when not to use it, or alternatives (e.g., if a soft-delete is needed).

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