Fetch the templates visible to the current actor for the template library: public templates, plus internal templates from the supplied `organizationId`, plus private templates owned by the actor's account. The visibility scope is always pinned to the actor and the supplied organization — the input filter can only narrow within that scope, never widen it.

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: single request with no automatic pagination, upstream `fields` used to bound data, and that provider errors must be treated as failures even on HTTP 200.

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 opening paragraph largely duplicates the title (also embedded in annotations), so it is somewhat redundant, though the trailing sentences about pagination and error handling are efficient and front-loaded with useful constraints.

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 an 8-parameter, nested-object read tool with no output schema, the description covers pagination behavior, error semantics, and scope constraints. It omits any mention of the `payload`/`payload_file` input alternatives and `account` credential selection, but the high schema coverage compensates.

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 88%, so the baseline is 3. The description restates the visibility-scope semantics that the schema's `filter.visibility` description already carries, adding little beyond the structured fields for parameters like `account`, `payload`, or `payload_file`.

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 (fetch) and resource (post templates) and carefully defines the visibility scope, which distinguishes it from the singular get_post_template sibling. It does not name siblings explicitly, but the scope definition makes the resource boundary clear.

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?

Explains that the input filter can only narrow within the actor-pinned scope, which usefully frames when the `filter.visibility` parameter matters. However, it gives no guidance on when to use this list tool versus get_post_template or search-style alternatives, leaving selection to inference.

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