cases_get_template

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Get' implies a read operation, but there is no mention of permissions, error cases, response structure, or whether the operation is safe/idempotent. This is insufficient for a tool with zero annotation support.

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, front-loaded sentence with no redundant words. It earns its place by stating the core action, though its brevity borders on under-specification. Still, it is concise and well-structured.

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 simple 2-parameter schema and existence of an output schema, the description is still too sparse. It fails to explain what a 'case template' is, why domain_id and template_id are required, or how this tool fits with sibling operations. The lack of any usage or parameter guidance makes it incomplete.

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 input schema has 0% description coverage—both domain_id and template_id lack any explanation. The description adds no meaning to these parameters, leaving the agent to guess their purpose, format, or relationship to the operation.

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 'Get case template details.' clearly states the action (get) and resource (case template details). It is specific enough to indicate a fetch operation for a single template, distinguishing it from list/create/update siblings, though it does not explicitly differentiate from similar generic template_get.

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 is provided on when to use this tool versus alternatives such as cases_list_templates or template_get. The description gives no context about prerequisites like needing a valid domain_id and template_id, nor any indication of preferred use cases.

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