get_template

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

No annotations are provided, so the description carries the full burden. It states 'Read', which implies a non-destructive operation, but it does not disclose additional behavioral details such as error behavior (e.g., not-found), permission requirements, or rate limits. The verb provides minimal transparency but nothing beyond that.

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?

A single, dense sentence with no filler: 'Read a single template by name.' The verb leads, the resource and scope are clear, and no word is wasted. Perfectly concise for the simple action it describes.

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 tool has one parameter fully documented in the schema and an output schema that describes the return, the description is nearly complete for a simple getter. It could mention what happens if the template does not exist, but that is a minor gap; the core information needed to call the tool correctly is 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?

The schema description covers 100% of the parameter (name), so the baseline is 3. The description's phrase 'by name' simply restates the parameter meaning without adding new semantics or syntax details beyond what the schema already provides.

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 states a specific verb ('Read'), a resource ('template'), and scope ('single... by name'), clearly distinguishing it from list_templates (which lists all) and template-related siblings like save_template and render_template. The purpose is immediately clear.

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 implies when to use it (when you need a single template by name), but it does not explicitly state when not to use it or name alternatives. There is no mention of preferring get_template over render_template or list_templates. Usage context is implied but not made explicit.

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