tenki_list_preview_urls

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

Annotations already cover readOnly/openWorld/idempotent, and the description adds valuable non-obvious behavior: client-side filtering that applies only to the fetched page, newest-first ordering, and pagination semantics via nextPageToken. The client-side filter caveat is especially important to prevent incorrect assumptions about server-side filtering.

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 main purpose, then the session_id caveat, then pagination. Each sentence carries distinct, necessary information with 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?

For a read-only paginated list with four optional parameters and no output schema, the description covers ordering, filtering scope, pagination tokens, and how to widen result sets. Combined with the annotations, an agent has everything needed to invoke the tool correctly.

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 100%, so the baseline is 3. The description enriches session_id by explaining the client-side scope, and it provides actionable pagination guidance for page_size and page_token. Workspace_id and bounds are already well-covered by the schema, so the description does not need to repeat them.

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 states a specific verb ('List'), a clear resource ('the workspace's preview URLs'), and an ordering ('newest page first'). This cleanly separates it from sibling preview URL tools like tenki_get_preview_url, tenki_create_preview_url, and tenki_delete_preview_url, making the operation unambiguous.

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?

Clear usage context is given: list preview URLs, optionally filter by session_id, paginate via nextPageToken, and raise page_size to widen results. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough that an agent can infer when this tool is appropriate.

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