Search Pages index

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

No annotations are provided, so the description must disclose behavior. It reveals that the search is against a local multilingual trigram index and that each result includes its sourceId, but it doesn't state whether the operation is read-only, whether authentication is required, or any other side effects. This leaves the safety profile largely uncovered.

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, immediately states the action, and includes a useful usage hint. Every word earns its place.

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 6 parameters, no annotations, and no output schema, the description is too sparse. It does not explain the return results beyond sourceId, nor filter semantics or limits, making it incomplete for confident usage.

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 0%, and the description only adds meaningful detail for sourceId (the special 'all' value). Other parameters (query, limit, locale, urlContains, maxSnippetChars) lack any descriptive context beyond schema constraints, leaving the user to infer their purpose from names.

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 identifies the tool as a search operation over a multilingual trigram index, specifying single-source or all-sources behavior via sourceId=all, and distinguishes search from sibling tools like fetch_indexed_section.

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?

It provides specific usage guidance ('Use sourceId all for cross-site search') and directs users to fetch_indexed_section with the returned sourceId. However, it doesn't explicitly state when not to use this tool or mention alternative search-related siblings.

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