elevenlabs_get_models

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful information beyond them: that each model's supported languages come back as part of the response, which matters because there is no output schema. It still says nothing about authentication or response shape.

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?

One sentence, front-loaded with the verb and resource, zero filler. Nothing could be removed without losing 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?

For a simple read-only, no-parameter listing tool whose annotations cover the safety profile, the description gives the resource and the payload content (models plus supported languages). Only a hint about which sibling to use for voices is missing.

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 single parameter api_key has 0% schema description coverage, and the description never mentions it. However, an api_key parameter is self-explanatory to an agent, so the practical cost is low. A 3 reflects that the description adds nothing but the parameter is unlikely to be misused.

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?

Specific verb ('List') plus a specific resource ('ElevenLabs TTS models and their supported languages'), so the agent knows exactly what this returns. It does not differentiate from siblings like elevenlabs_list_voices or elevenlabs_get_voice, which is the only thing holding it back from a 5.

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 gives no when-to-use guidance, no mention of alternatives such as elevenlabs_list_voices, and no prerequisites. At best the phrase 'supported languages' hints that it is used to pick a model before TTS, but that is inference rather than stated guidance.

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