togetherai_list_models

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

No annotations exist, and description only states the tool lists models—a read operation. It lacks disclosure of authentication requirement (though schema shows api_key required) and any potential behavioral traits like rate limits or response structure.

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?

Single sentence efficiently communicates tool purpose with no superfluous content.

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 listing tool with one parameter and no output schema, the description is largely complete. Minor gap: does not specify output format (e.g., model IDs vs. full objects), but the phrase 'list all available models' sufficiently conveys intent.

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 coverage is 100% with one parameter (api_key). The description adds no extra meaning beyond the schema's description of the parameter, warranting the baseline score of 3.

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?

Description explicitly states the tool lists all available models on Together AI, including specific types (chat, completion, embedding, image), clearly distinguishing it from sibling tools like togetherai_chat_completion.

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?

Description implies usage for viewing available models but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare with alternatives.

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