search

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

Discloses it returns a list of documents, not full content. No annotations provided, so description carries full burden. Does not mention permissions or rate limits, but acceptable for a search tool.

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?

Two efficient sentences with zero waste. Front-loaded with purpose, followed by usage guidance and alternative. Perfect structure for quick comprehension.

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?

Simple tool with 2 params and no output schema. Description fully explains purpose, return type, next steps, and alternative. No gaps given the tool's complexity.

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 covers both parameters with descriptions. Description adds context that query is for function names, class names, keywords. Baseline 3 due to high schema coverage; limited extra value.

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?

Description clearly states it searches MQL5 documentation (function names, class names, keywords). It distinguishes from siblings by noting it returns a list and suggests using 'get' for content and 'smart_query' for direct answers.

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 tells when to use (search docs) and when not to (use smart_query for direct answers). Provides workflow: call get to retrieve content. No exclusions needed.

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