superset_report_delete

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

The description discloses that the delivery schedule will be stopped, which is useful. However, it does not state whether deletion is irreversible, what permissions are needed, or what happens if confirm_delete is false. Given no annotations, more disclosure would be expected.

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?

Two short sentences plus an args list. Every sentence adds value; the structure is clear and front-loaded with the primary action.

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?

The tool is simple but the description omits critical behavioral details such as irreversibility, the exact semantics of confirm_delete (must be true?), and the return value. The output schema may cover the return, but the confirm_delete ambiguity is a notable gap.

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 description explains report_id as 'Report ID to delete' and confirm_delete as 'Deletion confirmation (REQUIRED)', adding meaning beyond the schema's bare types. However, the schema marks confirm_delete as optional with a default of false, so the 'REQUIRED' label is ambiguous and could mislead.

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?

Clearly states it deletes a report/alert, and specifies the consequence that the delivery schedule is stopped. Differentiates from report_create/update/get/list by naming the delete operation.

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 explicit when-to-use vs alternatives, but the description implies its purpose by naming 'Delete' and the effect. The confirm_delete argument is marked REQUIRED, giving some usage guidance, though no exclusions or alternative recommendations.

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