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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'execute' but does not indicate whether the operation is read-only, has side effects, requires authentication, or is rate-limited. There is no mention of error conditions or consequences of invalid variables. This is a significant gap for a tool that likely performs an analysis run.

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 two sentences, front-loaded with the core purpose and followed by a practical prerequisite. Every sentence serves a purpose, with no fluff. It is concise and well-structured.

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 has an output schema, so return values are covered. The description references get_templates, which is essential for correct usage. However, it does not explain what happens if variables are missing or mismatched, nor does it mention the platform parameter. Given the output schema and the prerequisite, it is adequate but could be more explicit about validation requirements.

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?

Schema description coverage is 100%, so the description adds marginal value beyond the schema. It does clarify that variables are template-defined ('required variables' from get_templates), which helps the agent understand the dynamic nature of the variables parameter. Platform is not mentioned, but the schema describes it. Baseline 3 is appropriate.

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 states the verb 'execute' and the resource 'template', and clarifies that variables are supplied. It implies a workflow with get_templates, but does not explicitly differentiate from get_template_details. Still, the purpose is specific and distinct from listing templates.

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 gives a clear prerequisite: 'First use get_templates to find available templates and their required variables.' This tells the agent to retrieve templates first, but does not mention when not to use this tool or alternatives like get_template_details. It provides context but lacks explicit exclusions.

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