List JsonFabrica templates

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose that the operation is a GET and returns a page shape, which signals a read-only, paginated call, but it does not explain default filtering by status, ordering, or how name/tags affect results.

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 dense sentence with no filler, front-loading the endpoint and core response shape. Every phrase earns its place.

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?

An agent can make a basic list call, but with 5 optional parameters, no annotations, no output schema, and only 20% parameter documentation, the description is incomplete. It does not clarify name matching, cursor usage, status defaults, or how tags combine with other filters.

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 only 20%: only `tags` has a description in the schema. The prose description adds nothing about `name`, `limit`, `cursor`, or `status`, so the description fails to compensate for the low schema coverage.

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 names the exact endpoint (GET /v1/templates) and clearly states it returns a paginated list of templates with `{ items, nextCursor }`. This distinguishes it from get_template, create/update/delete, and list_sequences by resource and verb.

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 verb 'List' and endpoint suggest it is the tool for retrieving multiple templates, and the paginated response implies it covers page-based browsing. However, there is no explicit statement of when to use it versus get_template, and no mention of alternatives or exclusions, so guidance is only implied.

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