confluence_search

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

With no annotations provided, the description carries the behavioral burden. It adds useful context by stating 'Results are bounded' and 'this server has no write operations,' which helps the agent understand output scaling and that the tool performs no mutations. It does not detail result shape or error behavior, but for a simple search tool this is reasonably transparent.

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 sentences, front-loaded with the core purpose, and contains no filler. The safety note about no write operations is brief and earns its place given the lack of annotations.

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 three-parameter search tool, the description plus schema covers the basic calling contract, but there is no output schema and the description does not mention what the search returns, pagination behavior, or any example CQL. 'Results are bounded' hints at limits but leaves practical expectations underspecified.

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 only 33% because only projection has a description. The main description mentions CQL, which gives some meaning to the cql parameter, but it does not explain how to construct CQL, what limit controls beyond its schema constraints, or how projection interacts with results. The description does not sufficiently compensate for the low schema coverage.

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 action and resource: 'Search Confluence with CQL.' This clearly separates it from sibling tools like jira_search_issues and confluence_get_page, since the resource (Confluence) and operation (search) are both explicit.

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 implies this tool should be used for searching Confluence, but it does not explicitly say when to choose it over siblings such as confluence_get_page or jira_search_issues. There is no when-not-to-use guidance or mention of alternatives.

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