Search Confluence content

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds that search uses CQL and supports pagination, but does not disclose result format, rate limits, permission requirements, or what happens with invalid CQL.

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 two tight sentences with no wasted wording. The core purpose is front-loaded, followed by a useful pagination note.

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?

With no output schema and zero parameter descriptions, the definition leaves important gaps: it does not explain CQL syntax, what expand does, or what the search response contains. An agent can make a basic call but lacks enough context to use the tool fully or interpret results confidently.

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 must compensate, but it only mentions start and limit for pagination. The required cql parameter's format and the expand parameter's purpose are left undocumented.

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 states a specific verb and resource: search Confluence content including pages, blog posts, and comments using CQL. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like confluence_get_page or confluence_rest.

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 only usage guidance is a note about using start and limit for pagination. There is no explanation of when to choose this search tool over alternatives such as confluence_rest, confluence_get_page, or confluence_list_comments.

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