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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful content-scoping context — no secrets, contacts or original files, metadata/approved fields only — which tells the agent what it will and will not see. It says nothing about pagination behavior or ordering, so it goes beyond annotations but not far.

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?

Two short sentences, front-loaded with the core action, and the scope disclaimer earns its place. The phrase 'through the existing application' is filler that slightly dilutes an otherwise tight definition.

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?

With three undocumented parameters, no output schema, and no mention of pagination or result shape, the definition leaves real gaps for a listing tool. The scope caveat is helpful but insufficient to make the definition complete for invocation.

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 0%, so the description must carry the load for limit, query and offset, and it does not mention any of them. There is no hint that 'query' is a text filter or that limit/offset paginate, leaving the agent to infer semantics from bare names and bounds.

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 verb 'Read' and resource 'flow templates' are stated, plus a field-scope qualifier. However the phrase 'through the existing application' is vague, and nothing distinguishes this from the sibling list_flow_content_templates or get_flow_template, which an agent could easily confuse it with.

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 statement of when to use this versus list_flow_content_templates or get_flow_template, and no prerequisites or exclusions. The only implicit guidance is the scope note that only metadata/approved fields are returned.

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