get_template

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Get details' implies a read-only operation, and the note to 'see the plan and rules before using' hints at additional context, but the description does not explain return format, side effects, or prerequisites in concrete terms.

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 organized into a clear summary sentence, a trigger list, and a parameter note. It is concise and front-loads the core purpose, though the instruction to 'see the plan and rules before using' is somewhat vague and could be more actionable.

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 tool with one required parameter and no nested objects, the description covers invocation and typical use cases well. However, there is no output schema and the description does not describe what the returned template details look like, which is a noticeable gap for an agent deciding whether this tool meets its need.

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 description coverage is 0%, and the schema only provides the title 'Template Id' for the required parameter. The description compensates by defining template_id as a template identifier and supplying concrete examples like 'deep_research' and 'code_review', adding value beyond the schema.

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 that the tool 'gets details of a specific session template,' identifying both the action and the resource. It distinguishes itself from list-oriented siblings like list_templates by emphasizing 'specific,' but it does not explicitly name or contrast a sibling tool.

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 an 'AUTOMATIC TRIGGERS' section with concrete cases: reviewing a template before creating a session, checking tasks in a template's plan, or responding to user questions about a specific template. It gives clear guidance on when to use the tool, though it does not mention when not to use it or suggest alternatives.

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