Get Raw Template

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

Description adds that it returns raw Markdown with placeholders intact, complementing annotations (readOnlyHint, idempotentHint). No contradiction. Could mention error cases, but sufficient for a simple getter.

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?

Two sentences, zero wasted words, front-loaded with key information. Highly efficient.

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 input (one enum param), strong annotations, and no output schema, the description sufficiently covers behavior. Slightly more detail on return format would improve, but not necessary.

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 a well-documented enum. Description adds no extra meaning beyond 'given artifact type'; baseline 3 is appropriate.

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?

Clearly states it returns the raw Markdown template for a given artifact type, preserving placeholders, and explicitly says it does not write files. This distinguishes it from write-oriented siblings like sdd_write_design.

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?

Implies use for retrieving templates before writing, confirmed by 'Does not write any files.' However, lacks explicit guidance on when to use vs alternatives or when not to use.

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