list_flow_templates

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

Since no annotations are provided, the description must carry all behavioral context. However, it offers no details on what 'published' entails, rate limiting, or expected response structure, making it low on behavioral transparency.

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 definition is highly concise, stating the exact function in one clear sentence without unnecessary padding or jargon. It is perfectly front-loaded.

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 complexity of the sibling tools, the definition is slightly incomplete. A sentence specifying whether this tool retrieves full data or only metadata would improve the agent's ability to choose the correct tool for the user's request.

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 coverage is 0%, meaning the description must add all semantic value. Since the description is a single declarative sentence, it adds no semantic meaning beyond what is already provided by the schema for the two pagination parameters. The score reflects the neutral baseline for low-value description on a simple 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 identifies the action ('List') and the resource ('ElevenCreative templates'). While the name is specific, the brevity means it does not explicitly differentiate the scope (e.g., public vs. internal) from similar list tools in the ecosystem.

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 other list/retrieve functions (like 'get_flow_template'). It merely states the function without context for optimal tool selection.

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