dero_docs_search

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

Annotations already establish read-only and non-destructive behavior. The description adds useful behavioral context beyond that: 'In-process — no network round trip,' ranked output with a specific field list, and a recommendation to use canonical_url/slug as citations. It does not contradict the 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 main purpose is front-loaded, followed by clearly-labeled usage, input requirements, and output sections. The prose is efficient, though the input requirements section partially duplicates schema information.

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 no output schema, the description appropriately documents return fields, ranking behavior, and in-process execution. It covers invocation constraints and citation guidance. It does not mention no-result behavior or explicitly route to sibling doc tools, but the essential information for calling the tool correctly is present.

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 coverage is 100%, so the schema already documents every parameter. The description adds minor context such as using product to 'reduce noise' and section to 'scope further,' but largely restates the schema's own descriptions without adding substantial new semantics.

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 precise action and resource: 'Search the bundled DERO documentation index across derod, tela, hologram, and deropay (145+ pages).' This clearly distinguishes search from sibling tools like dero_docs_get_page or dero_docs_list, which retrieve or enumerate rather than search.

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 'When to call' section explicitly states when to use the tool: when authoritative docs are needed, before constructing citations, and before explaining DVM, RPC methods, TELA contracts, Hologram simulator, or DeroPay webhooks. It gives clear context but does not explicitly identify when to use sibling alternatives instead.

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