get_templates

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

With no annotations, the description carries the full burden. It discloses pagination, efficient handling of large result sets, and transformation into standardized GetTemplatesElement objects. This adds meaningful behavioral context beyond just 'get templates' and implies a read-only, side-effect-free operation.

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 reasonably sized but has redundancy: the first and second sentences both say 'Get/Retrieves all templates.' It could be tightened to one sentence followed by the use-case and pagination details. Not zero-waste, but not overly verbose.

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 tool with one optional parameter and an output schema, the description is quite complete. It covers purpose, use cases, pagination behavior, and output standardization. The output schema covers return structure, so no need to detail return values in the description.

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 input schema already provides full coverage (100%) with a description and enum values for template_type. The description only adds 'optional filtering by template type,' which is redundant with the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Get all templates from Automation Studio' with a specific verb and resource, and further clarifies optional filtering by template type. This distinguishes it from sibling tools like describe_template (single template) or render_template (using a template).

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 use when needing to list all templates, and mentions optional filtering, but does not explicitly state when not to use it or compare to alternatives like describe_template or get_command_templates. The usage context is clear but lacks explicit exclusions or alternative guidance.

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