Get Information Pages

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

No annotations are provided, so the description carries the burden. It usefully discloses the return shape ('title and content preview') and the search target ('title text'), but says nothing about pagination, result limits, whether the search is a substring/prefix match, or that content is truncated to a preview rather than full body. Partial disclosure only.

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 short sentences, front-loaded with the resource and return shape, with the search behavior appended. No filler, though the second sentence is terse enough to feel slightly clipped rather than complete.

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 further, and the description covers what the tool lists and how to filter. The remaining gap is behavioral detail (pagination, match semantics) rather than core completeness.

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% and the single 'search' parameter has no description in the schema. The description compensates by stating 'Search by title text', which tells the agent what the parameter matches against, but omits matching behavior (substring vs exact), case sensitivity, and what an empty/default value returns.

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 ('List') and resource ('CMS/information pages') with examples of what those pages are, and distinguishes itself from the singular sibling get_information_page by the plural/listing framing. It does not explicitly name that sibling as the alternative, so differentiation is implied rather than stated.

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?

Usage is implied by the description ('list pages ... search by title text'), but there is no explicit guidance on when to use this versus get_information_page for a single page or versus get_seo_urls/get_categories for related lookups. Nothing states prerequisites or exclusions.

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