confluence_search_pages

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

No annotations provided, but the description explains pagination via cursor, default and max limits, and mentions CQL operators. It is transparent about search behavior, though could explicitly state it is read-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?

Description is concise, uses organized sections (Args:), and front-loads the purpose. No unnecessary sentences; each sentence adds value.

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?

Covers all parameters, return values, and pagination. Lacks error handling or mention of rate limits, but for a search tool it is fairly complete given the complexity.

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 has 0% description coverage, but the description thoroughly explains each parameter: query (with examples), limit (default, max), and cursor (for pagination). Adds significant meaning beyond the schema.

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 explicitly states the tool searches Confluence pages using CQL, and lists the returned data (titles, IDs, spaces). It is the only search tool among siblings, so no confusion with alternatives.

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 description provides examples of CQL queries and explains simple text fallback. It gives clear usage context, though it does not explicitly state when not to use or compare with other tools like confluence_list_pages.

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