GetFISExperimentTemplate

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation ('retrieves') but says nothing about permissions/IAM requirements, what happens when the ID does not exist, or rate/throttling behavior. For a lookup tool with zero annotation coverage, this is thin.

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 first two sentences are redundant, both saying it retrieves details of one template by ID. The Args/Returns boilerplate is standard but adds little, and the actual meaning is spread across duplicated prose rather than front-loaded once.

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 simple one-parameter read tool this is minimally adequate, but with no output schema the description should say more about what 'details' contains (e.g., action targets, role ARN, stop conditions) and how a missing ID is surfaced. It leaves those gaps open.

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 coverage is 100% and the single parameter 'id' is fully documented in the schema, so the baseline is 3. The description restates 'identified by its ID' without adding format, validation, or sourcing details beyond the schema.

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?

States a specific verb ('Get') and resource ('experiment template') plus the scoping key (its ID), so the agent knows it is a single-item retrieval. It does not, however, distinguish itself from the sibling GetFISExperiment, which retrieves an experiment rather than a template; the template-vs-experiment distinction is only inferable from the name.

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 only says what it does, not when to choose it over GetFISExperiment or ListFISExperimentTemplates. No prerequisites, no exclusions, no alternative routing is offered, leaving the agent to infer usage entirely.

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