toxic_flow_auditor__audit_catalog

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

No annotations accompany this tool, so the description carries the full disclosure burden. It states the detection logic (untrusted content + sensitive data + exfiltration/destruction on one server) and the output form (A–F grade), but says nothing about read-only behavior, permissions, or whether the catalog is transmitted anywhere.

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 compact sentences: the first defines scope and detection criteria, the second gives the return. The function and its output are front-loaded with zero filler.

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 two-parameter analysis tool with no output schema, the description supplies the input contract and states the return (a grade), which is adequate. It could be more complete on the meaning of the A–F scale or the trifecta-signal detail, but nothing essential to invoking it is missing.

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 coverage is 100% for both parameters (label, catalog) and the schema already documents their formats, so the description is not obligated to repeat them. It adds no syntax, size, or format detail beyond what the schema provides, giving the baseline 3.

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?

Specific verb ("Audit") plus a precisely-scoped resource ("tools/list-shaped JSON catalog") and a named detection target (the lethal trifecta). This clearly distinguishes it from toxic_flow_auditor siblings scan_source/scan_file/scan_directory, which consume other input types.

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 stated input shape (a tools/list JSON catalog) makes the use case evident and differentiates it from the source/file/directory scanners. However, no alternative is named explicitly and no when-not guidance is given, so an agent must infer routing from the input contract rather than being told.

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