watch_keywords

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

With no annotations, the description must fully disclose behavior. It mentions searching and displaying new/duplicate results, but does not clarify if the tool is read-only, whether it triggers alerts, how duplicate detection works, or any authentication requirements. Behavioral disclosure is minimal.

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 consists of two concise sentences: the first delivers the core purpose (keyword monitoring, search, new/duplicate display), and the second emphasizes multi-keyword support. No superfluous content.

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?

The description covers the main function and parameter semantics are fully handled by the schema. However, since there is no output schema, the description should specify the return format (e.g., whether it returns a list with status flags). The mention of 'new/duplicate display' gives a hint but is incomplete for an agent to fully understand the output.

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?

All parameters have schema descriptions (100% coverage), so the schema already documents their meaning. The tool description adds overall context but does not provide additional parameter-level insights beyond what is in the schema. Baseline score of 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 states it searches recent N-day announcements for specified keywords and marks new/duplicate, with multi-keyword monitoring. This is clear and specific. However, it does not explicitly differentiate from the sibling tool 'search_it_bids', leaving the agent to infer the distinction.

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 like 'search_it_bids' or other siblings. The description lacks explicit when-to-use or when-not-to-use instructions.

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