confluence_search_cql

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

The description explicitly shows 'GET', which signals a read-only search operation, and identifies the API path. However, with no annotations, it leaves important behavioral details unmentioned: return shape, pagination behavior, excerpt handling, and whether the search covers pages, blog posts, attachments, or other content.

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?

The description is extremely short and front-loaded, with no filler words or redundant phrasing. It is appropriately compact for a simple search tool, though the brevity does sacrifice useful explanatory content that is penalized elsewhere.

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 four-parameter tool with no annotations and no output schema, the description is incomplete: it omits valid CQL syntax guidance, return value structure, pagination semantics, and the scope of searchable content. The endpoint and name only provide basic orientation, not enough for reliable autonomous invocation.

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?

The description adds no meaning to any of the four parameters; the only parameter documentation is the cql example in the schema. With schema description coverage at only 25%, the description was expected to compensate for the undocumented limit, start, and excerpt parameters, but it does not.

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 names a specific operation, 'CQL search', and supplies the REST endpoint, making it clear this tool runs Confluence Query Language searches. It is sufficiently distinct from sibling search tools like jira_search_jql and gitlab_search, though it does not spell out what content types are searched.

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?

There is no guidance on when to use this tool instead of alternatives such as confluence_get_pages_in_space, jira_search_jql, or gitlab_search. The endpoint is provided, but no conditions, exclusions, or contextual recommendations are given.

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