confluence_cql_search

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

No annotations provided, but the description discloses pagination behavior (cursor-based), output trimming by default, and the option to get raw response via full=true. It lacks mention of error handling or permissions but covers key usage behaviors.

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?

Three concise sentences: purpose, usage context, and behavioral details (pagination, trimming). No fluff, front-loaded with key information.

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?

Without output schema, the description adequately covers input (CQL, pagination, trimming) and expected behavior. Could mention return format or error handling, but the core context for using the tool is present.

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 100%, but the description adds significant context: explains CQL syntax with examples, clarifies trimming vs full response, and describes cursor usage for pagination. This goes beyond the schema's brief descriptions.

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 clearly states the tool searches Confluence using CQL, lists searchable content types (pages, blog posts, attachments, comments), and implies advanced query capability. This distinguishes it from sibling search tools like confluence_search_content.

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 advises using this for 'advanced searches' and gives CQL examples, implying it for complex queries. However, it does not explicitly state when to prefer simpler alternatives or when not to use it.

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