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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior. The description adds valuable scope: only metadata/approved fields are returned, and secrets, contacts and original files are excluded. It also implies authorization filtering. This goes beyond annotations without contradicting them.

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 sentences, front-loaded with the core action, followed by a clarifying scope note. No filler or 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?

While the description clarifies data scope, it omits any guidance on the optional parameters and pagination, which are essential for a list operation. With no output schema and no parameter descriptions, the definition is materially incomplete for correct 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 coverage is 0% – none of the three parameters (limit, query, offset) have descriptions. The tool description does not mention any parameter or explain their purpose, so it adds no meaning beyond the bare schema. An agent must guess how to use query, limit, and offset.

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 'Read' and resource 'flow content templates', but does not differentiate from nearby siblings like list_flow_templates or get_flow_template. The clarification about metadata-only is useful but doesn't resolve what a 'content template' is versus a regular template.

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?

No explicit when-to-use or when-not-to-use guidance. The description doesn't reference alternatives or conditions that select this tool over list_flow_templates. The phrase 'through the existing application' is too vague to guide selection.

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