sdcloud_list_templates

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

No annotations provided; description mentions support for pagination, filtering, and sorting, which adds some behavioral context. However, it does not explicitly state it is read-only or disclose any other behavioral traits like authorization needs or rate limits.

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, clear sentence with no superfluous words. Efficiently conveys the core functionality.

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?

No output schema; the description does not explain the return format or structure of the listed templates. For a list tool, this is a significant gap, as agents need to know what data fields to expect.

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 all parameters described. The description does not add significant extra meaning beyond the schema; it only summarizes the optional features. Baseline 3 is appropriate.

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 clearly states 'List configuration templates' with specific verb and resource. It distinguishes from sibling tools like 'get_template' and 'delete_template' by using 'list'. Mention of optional pagination, filtering, and sorting adds specificity.

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?

No guidance on when to use this tool versus alternatives such as 'get_template' for a single template or other list tools. No when-not or explicit context provided.

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