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

The annotations already establish a read-only, idempotent, non-destructive operation, while the description adds useful payload scope through 'Full template' and the included 'train' execGraph. It adds little else about retrieval behavior, such as lookup failures or the implications of openWorldHint, but this is adequate for a simple read.

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 single compact sentence front-loads the full-template scope and key execGraph, then identifies its consumers. Despite dense abbreviations, every part contributes useful selection or invocation information without repetition.

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 one-parameter read with complete input documentation, an output schema, and safety annotations, this supplies the remaining context needed to invoke it correctly. The schema covers ID discovery, while the description covers payload purpose and downstream compatibility.

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 fully documents template_id, including its discovery through catalog.templates and an example value. The description adds no further parameter semantics, so the 100% schema-coverage baseline 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?

Together with the title, the description makes clear that this retrieves a full pipeline template containing the 'train' execGraph. The 'Full template' wording implicitly distinguishes it from catalog.templates, but that sibling is not explicitly contrasted as the list or discovery operation.

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?

Naming execution.run and pipeline.validate gives concrete downstream uses for the returned template. It does not provide when-not guidance, such as when catalog.templates is sufficient for browsing or selecting a template.

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