Tez Search

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

With no annotations provided, the description must convey behavior. It only says 'semantic search', which suggests a read-only operation but does not explicitly state side effects, permissions, or whether results are limited in any way. This is adequate but not fully transparent.

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 directly conveys the tool's scope without unnecessary detail or repetition.

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?

It provides the essential context that this is a cross-source search tool, which helps select among siblings. It does not mention output format or result handling, but for a search tool with the given schema, the context is mostly sufficient.

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 covers all three parameters with clear descriptions. The tool description does not add extra meaning beyond the schema, so it meets the baseline for fully covered parameters without enhancing understanding.

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 states a specific verb ('search'), specifies the resource ('Tezos documentation, TZIPs, and protocol source'), and highlights the cross-source nature, clearly distinguishing it from sibling tools that target individual sources.

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 implies usage for cross-source queries by calling out 'cross-source semantic search', and the sibling tools for specific sources are implicitly alternatives. However, it does not explicitly state when to use this versus the specific-source tools, leaving some inference needed.

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