sdcloud_list_template_mappings

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

No annotations provided; the description discloses pagination, filtering, and sorting capabilities but does not mention rate limits, default behavior, or whether results are ordered. It adds some useful info but not comprehensive.

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, no wasted words. Front-loads the core purpose and optional features efficiently.

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 list tool with 6 params and no output schema, the description is adequate but minimal. It lists features but doesn't describe return format, error handling, or typical use cases. Could be more complete.

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 high (83%), so baseline is 3. The description adds minimal beyond the schema, merely restating that the tool supports pagination/filtering/sorting without explaining parameter syntax or constraints.

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 the verb 'List', the resource 'device mappings for a template', and the optional capabilities 'pagination, filtering, and sorting'. It distinguishes from siblings like 'get_template_mapping' (single) and 'batch_save_template_mappings' (write).

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 implies usage for listing mappings but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusion criteria. With many sibling tools, more context would help.

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