getTemplates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that no query is needed and specifies the return fields, aligning with and complementing the annotations without contradiction.

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 two concise sentences that front-load the purpose and return fields, then provide sibling differentiation. Every sentence adds value without waste.

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 simple list-all tool with no required parameters and no output schema, the description covers everything: purpose, return fields, and alternatives. No gaps are present.

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 has one dummy parameter with 'Not used' description; the description states 'クエリ不要' (no query needed), confirming the parameter is irrelevant. This fully explains the parameter semantics.

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 it retrieves a list of all templates (shop page HTML/CSS designs, used or unused) without query, returning specific fields. It explicitly distinguishes from sibling tools getTemplatePage, getTemplatePreview, and updateTemplatePage.

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 explicit when-to-use: for listing all templates, and contrasts with alternatives for specific actions (getTemplatePage for HTML/CSS, getTemplatePreview for preview URL, updateTemplatePage for updates). This gives clear guidance.

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