aap_list_job_templates

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds valuable behavioral detail: the return type (JSON string) and the specific fields included in each result, which goes beyond the structured 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 structured docstring with Args and Returns sections is well-organized and easy to scan. While it repeats parameter information, every sentence serves a purpose and there is no fluff. Slightly longer than necessary but still concise.

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 description covers the listing action, optional filters, and return structure in sufficient detail for a read-only list tool. It does not mention ordering or pagination behavior beyond the page/page_size parameters, but these are already in the schema. The presence of an output schema also lessens the burden.

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 explicitly lists all five parameters with types and meaning, including page/page_size which the schema describes only with types/defaults. Given the schema's 0% coverage at the top level, the description fully compensates and even clarifies filtering semantics.

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 'List AAP job templates with optional filtering,' using the specific verb 'List' and naming the resource 'AAP job templates.' This clearly distinguishes it from siblings like aap_get_job_template (retrieve single) and aap_create_job_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 usage through 'with optional filtering' and the parameter list, but it does not explicitly state when to prefer this tool over alternatives such as aap_get_job_template for a single template or aap_launch_job_template for execution. There is no when-not guidance.

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