getMockupTemplates

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

With no annotations provided, the description carries full burden. The verb 'Get' clearly indicates a read-only retrieval operation, which is transparent and non-destructive. Yet it does not disclose details such as what 'available' means, whether the product must exist, or what the response contains, leaving some behavioral gaps.

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 concise sentence of seven words, front-loaded with the verb and resource. Every word is necessary, and there is no redundant or extraneous information.

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?

The tool is simple with one required parameter and no output schema, so the description is partially complete. It states the purpose and the required input, but it does not describe the return value format, pagination, or the meaning of 'available'. Without an output schema, the description should provide more detail about what the caller receives.

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 product_id described as 'Product ID'. The description adds 'for a product' which reinforces the parameter's purpose but does not provide additional semantics beyond what the schema already states. The baseline of 3 applies because there is no meaningful value added.

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 tool retrieves mockup templates for a product using the specific verb 'Get' and resource 'mockup templates'. It is distinguishable from sibling tools like getProduct or createMockupTask because no other sibling references mockup templates, though it does not explicitly compare itself to alternatives.

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 phrase 'for a product' implies the tool is used when you have a product_id and need its mockup templates. However, it does not provide explicit guidance on when to use this tool versus alternatives, mention exclusions, or describe required prerequisites beyond the schema.

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