delete_docqa_assistant

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

The description explicitly tags the action as a mutation, mentions resource deletion scope, and requires confirmation. With no annotations provided, the description carries the full burden and performs reasonably well, though it could detail what resources are associated.

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 concise sentence that front-loads the purpose and includes necessary detail. No unnecessary 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 delete tool with two simple parameters and no output schema, the description is complete: it specifies the action, scope, and required confirmation. Sibling tools are covered by distinct names.

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 description coverage is 100%, so the description adds no new meaning beyond what the schema already provides. The description repeats the confirmation requirement, but the schema already says the same.

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 Doc-QA assistant and all associated resources, distinguishing it from sibling tools like delete_docqa_file. The verb 'eliminar' and resource 'asistente Doc-QA' are specific.

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 it requires confirmation (pass confirm=true), which is a key usage guideline for a destructive action. However, it does not explicitly state when not to use or mention alternatives.

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