List VLM Prompt Tasks

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

No annotations are provided, so the description carries the burden. It discloses the HTTP endpoint (GET /sdapi/v1/vqa/prompts) which implies a read-only operation, but doesn't describe return format, pagination, or any side effects. The GET method is a useful behavioral hint, but more could be said about what 'task prompts' means.

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 sentence, front-loaded with the action ('List task prompts'), and includes the endpoint for reference. No wasted 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 simple list tool with one optional parameter and no output schema, the description is adequate but could be more complete. It doesn't explain what 'task prompts' are, how they relate to VLM models, or what the response looks like. Given the simplicity, a 3 is fair.

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% (the only parameter 'model' is described as 'VLM name to filter tasks for'). The description adds minimal value beyond the schema, but the schema already fully documents the parameter. Baseline 3 is appropriate.

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 lists task prompts for a VLM, with a specific verb ('List') and resource ('task prompts'). It distinguishes from sibling tools like sdnext_list_vqa_models (which lists models) and sdnext_vqa (which likely runs VQA), though it doesn't explicitly name them.

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 (listing prompts for a VLM) but provides no explicit guidance on when to use this vs alternatives. The optional 'model' parameter suggests filtering, but no context on when filtering is needed or how it relates to other VQA tools.

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