Search Confluence

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds meaningful behavioral details: filters are combined with AND, and pagination is handled via start/limit with a hasMore indicator in the response. This enriches the agent's understanding of the tool's behavior without repeating annotation info.

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 ('Search Confluence'), then immediately provides essential usage details. Every sentence earns its place with no wasted words.

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 14 parameters and existing output schema, the description covers the key cross-cutting behaviors (filter combination, pagination) adequately. It does not mention the save_path parameter, but that is documented in the schema, and the output schema reduces the need to describe return values.

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?

With 86% schema description coverage, the schema already documents most parameters. The description adds global semantics: 'All filters are combined with AND' explains how multiple query params interact, and the pagination note clarifies start/limit usage, going beyond the individual parameter descriptions.

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 'Search Confluence' with a specific verb and resource, clearly distinguishing this tool from sibling tools like get_content_by_id or get_spaces, which are direct lookups rather than general search. The purpose is unambiguous.

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 gives 'All filters are combined with AND' and pagination guidance, providing clear context on how to use the tool's parameters. However, it does not explicitly state when to prefer this tool over siblings or provide exclusions, leaving some implied usage based on the name 'search'.

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