comfyui_get_model_metadata

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. However, the description adds no additional behavioral context, such as what the metadata contains, potential errors, or rate limits. It simply restates the function name and arguments, providing no value beyond the annotations.

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 very concise: a one-sentence purpose followed by a two-item argument list. It is front-loaded with the key verb phrase and uses a clean, structured format. Every sentence earns its place without unnecessary verbosity.

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 tool with two string parameters, an output schema, and rich annotations, the description is mostly sufficient. It explains the purpose and parameters clearly. However, it lacks any usage context or behavioral details (e.g., what metadata fields are returned), though the output schema likely covers return values. Overall, it is complete enough for a basic metadata getter.

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 schema has 0% description coverage, but the description compensates by explaining both parameters: folder is 'Model folder type (checkpoints, loras, vae, etc.)' and filename is 'Name of the model file.' The folder examples (checkpoints, loras, vae) add practical meaning beyond the raw schema, making the parameters more understandable.

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's function: 'Get metadata for a model file.' It specifies the resource (model file) and the verb (get), which is unambiguous. However, it does not explicitly differentiate this from sibling tools like comfyui_list_models or comfyui_get_model_presets, so it lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only lists the arguments, which implies the user needs to supply folder and filename but gives no context about the typical use case or when other tools might be more appropriate.

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