sdcloud_get_template_mapping

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

With no annotations, the description must disclose behavioral traits. 'Get' implies a read-only operation, which is standard, but no details are given about idempotency, error conditions, or dependencies. While it is likely non-destructive, the lack of explicit safety context lowers the score.

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 description is a single sentence with no unnecessary words. It is front-loaded with the key action and resource.

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 lack of output schema, 2 parameters without descriptions, and no annotations, the description is severely incomplete. It does not explain what a device mapping is, what the return value looks like, or any prerequisites (e.g., existence of template and device).

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 description coverage is 0%, and the description adds no meaning to the two required parameters ('device_id', 'template_id'). No hint about expected format, source, or relationship to other resources.

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 uses a specific verb ('Get') and specific resource ('a single device mapping for a template'). It clearly distinguishes the tool from siblings like 'list', 'delete', 'update', and 'batch save' by indicating it retrieves one specific mapping.

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 alternatives. Sibling tools like 'sdcloud_list_template_mappings' or 'sdcloud_update_template_mapping' exist, but no context is given for selection.

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