producer_list_models

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

The description discloses that the tool returns a table of models with versions and features, which is the expected behavior for a list operation. Without annotations, it adequately informs the agent of the outcome. No side effects are mentioned, but listing is inherently non-destructive.

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 concise, direct, and front-loaded with the core purpose. Every sentence adds value, and there is no extraneous information.

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 the tool has no parameters and an output schema exists, the description is complete. It explains what the tool returns and why it is useful, covering all necessary context for an agent.

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 tool has no parameters and the schema coverage is 100%. The description adds meaning by explaining the purpose of the output, which is sufficient for a parameterless tool.

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 this tool lists all available Producer/FUZZ models and their capabilities. While it is straightforward, it does not explicitly differentiate itself from siblings, but the distinction is obvious given that siblings are about generating music or other actions.

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 includes 'Use this to understand which model to choose for your music generation,' providing clear context for when to use it. However, it lacks explicit statements about when not to use it or alternatives.

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