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

The description explicitly states the tool is read-only and returns matching titles, snippets, Space details, and URLs without changing content. This goes beyond the readOnlyHint annotation by detailing the exact nature of the output and reaffirming no side effects.

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 brief, consisting of two sentences that cover the tool's purpose, scope, read-only nature, and output contents. There is no redundant or unnecessary information.

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 simple search tool, the description provides complete context: what it searches, when to use it, that it's read-only, and what it returns. It sufficiently equips an agent to decide when and how to invoke it without needing additional details.

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 parameter schema already covers query and per_page with clear descriptions. The description does not add significant semantic details beyond what the schema provides, so a baseline score 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 explicitly states the tool's purpose: searching documents across all accessible Spaces. It distinguishes itself from search-space-documents by mentioning 'rather than one known Space,' making the resource and scope clear.

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 directly instructs when to use the tool: when the user wants to search across every accessible Space. By contrast, it implies that for a single known Space, search-space-documents should be used, providing clear usage guidance.

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