confluence_search

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

No annotations are provided, and the description does not disclose behavioral traits such as rate limits, authentication requirements, or whether the tool is read-only. As a search tool, it is presumed non-destructive, but this is not explicitly stated, leaving the agent without important context.

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 sentence that is front-loaded with the verb 'Search'. It is concise with no unnecessary words. However, it could be slightly expanded to include important context like pagination.

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 5 parameters and no output schema, the description is incomplete. It does not explain the return format, pagination behavior (cursor), or result ordering. For a search tool, this leaves significant gaps for the agent.

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 80%, with descriptions for query, cursor, spaces, and content_types. The tool description adds no additional meaning beyond these schema descriptions. Baseline 3 is appropriate.

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 'Search Confluence content (pages, blog posts, etc.) by text query.' It specifies the verb (search), resource (Confluence content), and scope (by text query). This differentiates it from sibling tools like confluence_get_page (retrieve a specific page) and confluence_list_pages_in_space (list pages in a space).

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 usage for text-based searching of Confluence content, but it does not explicitly state when to use this tool versus alternatives like confluence_get_page for a single page or confluence_list_pages_in_space for all pages. No guidance on when not to use it or exclusions.

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