get_flow_template

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. "Read" implies a safe retrieval operation, but the description does not disclose permissions, error behavior, whether missing templates fail gracefully, or what the returned definition and input schema contain beyond a brief mention.

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 a single front-loaded sentence with no wasted wording. Its brevity is appropriate for a simple getter, though it is under-specified rather than optimally complete.

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 retrieval tool with no output schema, the description states what is returned at a high level. However, it does not compensate for the absent annotations or the undocumented template_id parameter, leaving gaps around identifier format and failure behavior.

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 only parameter, template_id, has 0% schema description coverage and no format or constraint details in the description. The description implicitly establishes that the ID identifies a template but adds no syntax, source, or validation meaning beyond that.

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 uses a specific verb, "Read," and a clear resource, "a template definition and its input schema." It is distinguishable from siblings like list_flow_templates and run_flow_template by focusing on retrieving one template's definition rather than listing or executing it, though it does not explicitly name those alternatives.

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?

There is no explicit guidance on when to use this tool versus list_flow_templates, run_flow_template, or get_flow_run. The usage is only implied by "Read a template definition," leaving the agent to infer prerequisites and appropriate contexts.

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