search_docs

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

No annotations are provided, so the description must disclose behavioral traits. It discloses the search scope and filtering capability, but does not specify return format, result limits, authorization requirements, or other behavioral details. This is a significant gap given the absence of annotations.

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 concise sentences, front-loaded with the core purpose and content scope. The second sentence adds filtering capabilities without redundancy. It achieves clarity in minimal words, earning a perfect score.

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?

The tool is a search across all docs, with schema covering the parameters adequately. However, the description does not explain return values, which is important since no output schema exists. The absence of authorization or result format details leaves the agent somewhat uncertain about the tool's behavior, but the core purpose is clear enough for basic invocation.

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?

Input schema covers all parameters with descriptions, so baseline is 3. The description adds context that type and category serve as filters, aligning with schema, but does not add meaningful detail beyond what the schema provides. The query parameter is adequately described in the schema, maintaining the baseline.

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 performs a search across all MAX documentation, listing specific content types (endpoints, models, guides, Bridge API, UI components). It distinguishes itself from sibling tools by covering all documentation types and offering filtering. The verb 'search' and resource 'docs' are specific and 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?

The description implies this is the broad search tool, while sibling tools are direct accessors, but it does not explicitly state when to use search_docs instead of specific getters. No explicit alternatives or exclusions are mentioned. This leaves the agent to infer usage context, which is clear but not explicitly guided.

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