search_confluence

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

With no annotations, the description carries the full burden of disclosing behavior. It only states that the tool 'searches,' which implies a read-only operation, but does not explicitly confirm this, nor does it mention return format, pagination, permissions, or rate limits. This is minimal disclosure.

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, well-structured sentence with no filler. It is front-loaded with the verb and resource, and every word contributes to understanding the tool's function. No unnecessary detail is included.

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 tool with no output schema and no annotations, the description is quite minimal. It does not explain what a successful search returns, how the 'limit' parameter affects results, or any potential error conditions. However, given the simplicity of the parameters and the straightforward nature of a search operation, it is borderline adequate but clearly has gaps.

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 schema provides full descriptions for both parameters (cql and limit), so the baseline is 3. The description mentions CQL but adds no additional meaning beyond what the schema already documents. It does not explain parameter syntax or edge cases beyond the schema's examples.

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 uses a specific verb ('Search'), resource ('Confluence pages'), and method ('CQL'). It clearly distinguishes this tool from sibling tools like get_confluence_page, create_confluence_page, and custom_query, which serve different purposes.

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 such as custom_query or get_confluence_page. There are no explicit when-to-use or when-not-to-use instructions, and no comparison to sibling tools, leaving the agent to infer the appropriate context.

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