confluence_search

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the basic search action and mentions CQL, but does not disclose what the response looks like, how pagination works, or any required permissions. The description adds no meaningful behavioral context beyond the function itself.

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 a single short sentence, but this brevity results from under-specification rather than effective conciseness. It omits crucial details that would require additional sentences to explain. The structure does not front-load information beyond the bare minimum.

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?

Given the lack of annotations and output schema, the description is profoundly incomplete. It does not explain how to compose CQL, what the returned data structure is, or how limit and start affect results. An agent would be unable to use this tool reliably without guessing or seeking external documentation.

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%, and the description does not explain any parameters. It refers to CQL but fails to clarify the roles of cql, limit, and start. The agent is left with only schema type constraints, which are insufficient for understanding how to build queries or interpret pagination parameters.

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's function: 'Search Confluence content with CQL.' This identifies the verb ('search'), the resource ('Confluence content'), and the method ('CQL'), effectively distinguishing it from sibling tools like confluence_get_page and confluence_create_page.

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 no guidance on when to use this tool versus alternatives. It does not mention that this should be used for general search queries instead of specific page retrieval, nor does it reference any sibling tools or conditions. Usage context is only implied by the tool's name.

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