describe_template

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

No annotations are provided, so the description carries full burden. It uses "Get" and "Retrieves," indicating a read-only operation, but doesn't disclose potential errors, permissions, or side effects. It adds context about template content and purpose.

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 three sentences, front-loading the core purpose. The list of fields is concise, and the last sentence adds useful context without any fluff.

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?

With an output schema present and a simple describe operation, the description covers the essentials. It explains what templates are used for, adding contextual completeness, but lacks explicit guidance on project scope or error behavior. Overall, it is sufficient for the tool's simplicity.

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 already describes both parameters (name and project) with clear descriptions, achieving 100% coverage. The description doesn't add extra parameter details, so baseline 3 applies.

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 opens with "Get detailed information about a specific template from Automation Studio," which clearly states the verb and object. It lists the specific fields retrieved, distinguishing it from other describe_* siblings like describe_session or describe_resource.

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 usage by stating "specific template" and describing what templates are used for, but it lacks explicit alternatives or exclusion criteria. It doesn't say when to use this instead of get_templates or describe_command_template.

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