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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the bar is lower. The description adds genuinely new behavior: the site must be connected, and a failed connection surfaces an error pointing to Wavelength settings.

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?

Three short sentences, front-loaded with the search action followed by chaining and failure context. Minimal waste, though the page_id sentence describes a return value rather than an input.

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?

With no output schema and annotations covering the safety profile, the description supplies the connection prerequisite, the error path, and how results chain into send_flow_to_confluence. Enough for an agent to call it correctly.

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 coverage is 100%, so query and space_key are already documented. The description only restates space_key's purpose as a hand-off to send_flow_to_confluence and introduces page_id, which is not an input parameter here, so it adds little parameter-level meaning.

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?

Specific verb+resource: 'Search the connected Confluence site for spaces and pages.' The Confluence scope cleanly separates it from sibling finders like find_jira_targets and find_notion_pages without needing to open a schema.

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?

Gives a clear downstream context: pass space_key to send_flow_to_confluence to create a page, or page_id to append to an existing page. This tells the agent what to do with results, though it never states when to prefer this finder over related siblings.

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