get_embeddings

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

The description discloses the read-only nature, the API endpoint used, and the folder context. Without annotations, it carries the full burden but is adequate for a simple list. It lacks discussion of error handling or behavior if the server is unreachable.

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 three sentences with no wasted words. The purpose is front-loaded, followed by technical details and a usage example.

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?

Given no output schema, the description adequately explains the return (embedding names) and how to use them. It covers essential context but could mention potential limitations or error scenarios.

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?

With no parameters, the baseline is 4. The description adds value by explaining the endpoint and usage beyond the schema, which already has 100% coverage.

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 textual-inversion embeddings installed on a ComfyUI server, specifying the endpoint and source folder. It distinguishes itself from sibling tools by being a dedicated read-only list 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?

The description indicates the tool requires a running ComfyUI server and takes no parameters. It provides usage context by explaining how to reference embeddings in prompts, but does not explicitly state when not to use it or suggest alternatives.

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