Search Probe Documents

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

The readOnlyHint annotation already covers safety, and the description adds context by stating it is a 'stub' and returns specific fields (IDs, titles, URLs). This provides behavioral insight beyond the annotation, though it does not elaborate on limitations like pagination or result counts.

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 a single concise sentence that states purpose, output, and usage guidance without any redundancy. It is front-loaded and immediately clear.

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 simple one-parameter search tool, the description covers its return values and relationship to fetch. The presence of an output schema and annotations reduces the burden, and the description fills the essential gaps.

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 schema has 100% coverage for the single 'query' parameter with a basic description. The tool description does not add any additional semantics beyond the schema, so baseline 3 applies.

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 that the tool performs a search, returns result IDs, titles, and URLs, and is specifically for probe documents. It distinguishes from the sibling tool 'fetch' which retrieves full text, making the purpose 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?

Explicitly says 'Use fetch to retrieve full text,' providing a clear alternative and when to use another tool. It also labels the tool as read-only, suggesting it is for search queries only, not for retrieval or modification.

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