NudeNet Censor

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

With no annotations provided, the descriptive burden is high, yet the description only states the action and methods. It does not disclose whether the tool returns a modified image, mutates the input, or requires specific SD.Next setup, leaving key behaviors undefined.

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, front-loaded sentence that efficiently conveys the core purpose and lists methods without fluff. It earns high marks for conciseness, though it could sacrifice a bit of brevity for additional context.

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 tool with six parameters, no output schema, and no annotations, the description is too sparse. It omits return behavior, prerequisite conditions, and how parameters like 'blocks' or 'overlay' interact with each other. This leaves significant gaps for an agent trying to use the tool correctly.

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 83%, so the baseline is 3. The description repeats the method enum (pixelate, blur, mosaic, overlay) but adds no new semantic meaning beyond what the schema already provides. It does not elaborate on parameter interactions or edge cases.

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 censors explicit regions using NudeNet, naming the specific API endpoint and listing available methods. This distinguishes it from other SD.Next tools, which are unrelated to censorship.

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 for censoring images but provides no explicit guidance on when to choose this tool over alternatives like sdnext_detect or sdnext_process_image. It does not mention any conditions or exclusions.

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