aap_get_job_template

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description aligns with 'Get'. It adds value by listing what details are returned (credentials, labels, survey spec, etc.), which is not visible in annotations.

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 compact, with clear Args and Returns sections. Every line adds value, and it is well-structured for quick parsing by an AI agent.

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?

The tool is simple with one parameter, strong annotations, and a clear return description. The description covers the essential aspects of what the tool does and returns, making it complete enough for agent invocation.

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 description repeats the schema's description 'Job template ID' for template_id, adding minimal new meaning. With the schema already providing the type and minimum, the description does not significantly compensate for the reported 0% schema coverage, but the parameter is simple and unambiguous.

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 full details of an AAP job template' with a specific verb and resource. It distinguishes from sibling tools like aap_list_job_templates by emphasizing 'full details' and listing the rich content returned.

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?

Usage is implied: use when you need full details of a job template. However, there is no explicit comparison to alternatives like aap_list_job_templates or aap_launch_job_template, nor any when-not-to-use guidance.

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