find

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

The description mentions a cost of $0.02 USDC, which is a behavioral trait, but it does not disclose whether the tool is read-only, destructive, or any side effects. With no annotations provided, the description carries the full burden, and it fails to describe key behavioral aspects beyond cost.

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 with no wasted words. However, it lacks structure such as front-loading the most critical information (e.g., cost first) and could be slightly improved in readability.

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?

Given the tool has one parameter, no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns, how results are presented, or how it differs from the sibling 'discover.' This lack of context hampers an agent's ability to use it appropriately.

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% with the 'intent' parameter described as 'Describe what you need.' The description adds 'in plain English,' which clarifies the input format but does not add substantial meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 'Intent-based discovery' and 'describe what you need in plain English,' which effectively conveys the tool's purpose as a natural language search tool. However, the sibling tool 'discover' could overlap, and the description doesn't distinguish them explicitly.

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 provides basic guidance to 'describe what you need' and mentions cost, but it does not specify when to use this tool versus alternatives like 'discover,' nor does it indicate when not to use it. No exclusions or context for selection are provided.

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