aztec_search_code

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

Only mentions regex support; lacks disclosure of read-only nature, pagination, rate limits, or any behavioral traits beyond what is obvious for a search tool, with no annotations to compensate.

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?

Three sentences efficiently convey purpose and use cases without fluff, front-loaded with the key verb+resource.

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?

Provides purpose and use cases but misses details like result format, maximum results hint, or limitations; acceptable for a straightforward search tool but not fully complete.

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 coverage is 100% and descriptions are adequate; the tool description adds no further parameter meaning beyond restating regex support already in schema.

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?

Clearly states it searches Aztec contract code and source files, supports regex patterns, and gives specific use cases like finding function implementations and examples, distinguishing it from sibling tools like aztec_search_docs.

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?

Suggests use for finding function implementations and examples but does not explicitly state when not to use or compare to alternatives like aztec_search_docs or aztec_list_examples.

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