kloakt_search

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

Given no annotations, the description explains the rendering and filtering behavior, including query and same-domain restrictions. It does not mention error scenarios or rate limits, but the core behavior is transparent enough for a search tool.

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?

Two sentences with no redundancy. The first sentence delivers the core action and output, the second provides usage guidance. Every part earns its place.

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 purpose, output format (absolute URLs with anchor text), and filtering options. It lacks details on pagination or what happens if no links found, but for a simple discovery tool it is adequately 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%, so baseline is 3. The description adds contextual value by stating that filtering is optional and referencing 'query substring' and 'same domain,' but does not go beyond the schema's descriptions significantly.

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 the tool discovers outbound links on a page, renders it, and returns absolute URLs with anchor text. It distinguishes from siblings like kloakt_extract by focusing on link discovery for navigation.

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?

Explicitly advises to use this tool to find where to go next before extracting, with an example of locating article links on an index page. This provides clear context and implies when not to use it.

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