faz_cancel_log_search

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

The description says 'delete a LogView task,' which is a destructive action, but annotations declare destructiveHint=false. This is a direct contradiction. The description also fails to disclose any other behavioral details, such as permissions or side effects, beyond what annotations already state.

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 with no unnecessary words. However, it is under-specified for the tool's complexity, so while it is structurally efficient, the brevity comes at the expense of critical information.

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?

Even with an output schema present, the description is too sparse. It doesn't explain the required tid parameter, the optional adom, or the cancellation behavior. It also contradicts annotations, making it incomplete for safe and correct use.

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 has 0% description coverage, with only names 'tid' and 'adom' and a required flag. The description provides no parameter semantics, so it doesn't help the agent understand what tid refers to (the task ID) or the role of adom. With low schema coverage, the description must compensate, but it does not.

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 action ('Cancel and delete') and the resource ('a LogView task'), along with the purpose ('to release FortiAnalyzer resources'). It distinguishes this tool from siblings like faz_start_log_search and faz_get_log_search by the specific action of canceling/deleting a task.

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 the tool is used when a LogView task is no longer needed and resources should be freed, but it provides no explicit when-to-use guidance, exclusions, or alternatives. Without context about when to choose this over related tools, agents must infer usage from the name and siblings.

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