search-confluence

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

With no annotations, the description carries the burden. It discloses automatic CQL enhancement for simple queries, which is valuable. However, it does not mention authentication needs, rate limits, or behavior on invalid queries.

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?

Two sentences, front-loaded with purpose, no filler. Every sentence adds value.

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?

Adequate for a search tool with 3 parameters, but lacks description of return format or how results are structured. Without an output schema, the description should cover this.

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 description adds significant meaning beyond the schema for the 'query' parameter by explaining automatic CQL enhancement. The other parameters are well-documented in the schema. Schema coverage is 100%, so baseline is 3, but the enhancement detail raises it to 4.

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 pages using CQL'. It differentiates from siblings by focusing on search with CQL, while others like get-confluence-page retrieve specific pages or ask-confluence-page likely answer questions based on a 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 explains when to use simple text vs. advanced CQL queries, but does not provide guidance on selecting this tool over sibling tools like ask-confluence-page or get-confluence-page.

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