direct_list_turbo_pages

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description's 'Read-only' simply restates that. The field enumeration (Id, Name, Href) is already conveyed by the output schema, so nothing beyond structured data is added – no mention of pagination behavior, total counts, or scope of the list.

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?

A single compact line with the payload shape front-loaded and the cross-tool hint second. Every clause is short and readable, though the semicolon-packed style leaves no room for the missing parameter/pagination context.

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 output schema exists, so return values need not be explained, but with 3 undocumented parameters at 0% coverage and only annotations covering safety, the definition omits how to filter (ids) and page (limit/offset) – essential operational detail for a list endpoint that can return up to 500 records.

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 carries the full burden for `ids`, `limit` (default 500) and `offset` (default 0). It never mentions filtering by ids or pagination, leaving an agent to guess from parameter names alone; only the 'use Id for direct_list_leads' phrase hints that ids are entity identifiers.

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?

Names the resource (Turbo pages) and enumerates the returned fields (Id, Name, Href), and points to the sibling consumer `direct_list_leads`, so the agent can tell what it retrieves and where its output goes. It lacks an explicit verb, but 'list_turbo_pages' plus the field list is 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?

Gives one concrete downstream usage rule ('use Id for direct_list_leads'), which is genuinely helpful routing. It does not say when to call this tool versus other list siblings, nor any prerequisites (agency client, account scope); usage is only implied.

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