search

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

With no annotations provided, the description must fully disclose behavioral traits. It only mentions 'uses the site search form', implying a web search but not describing what results look like, pagination, rate limits, or side effects. This is insufficient for an agent to understand its behavior.

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, front-loaded sentence with no wordiness. It efficiently conveys the tool's purpose. However, it could be slightly more structured by separating search scope and parameter hints, but overall it is concise.

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 3 parameters and no output schema, the description lacks critical details like what the search returns (threads, posts?), the meaning of limit (e.g., max results or pages), and behavior of title_only. The tool's complexity demands more context for safe use.

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 description adds context to the keywords parameter by mentioning 'ASX codes' (not in schema). However, it does not clarify the limit or title_only parameters. Schema coverage is 67%, so the description partially compensates but leaves gaps.

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 it searches HotCopper for keywords or ASX codes using the site search form. The verb 'search' and resource 'HotCopper' are specific. However, it does not distinguish from sibling tools like stock_threads or get_thread, which could lead to confusion about when to use each.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., stock_threads, get_thread). There is no mention of prerequisites, limitations, or when not to use it. The description only states what it does, not when it is appropriate.

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