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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description adds the one thing annotations cannot: the return shape ('tool names, what they do and links'), which matters because there is no output schema. It omits auth/rate-limit context, keeping it short of a 5.

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?

Front-loaded with the core action, then examples, then the empty-input behavior, then the sibling handoff — each sentence carries distinct information. The examples are the highest-value content and are placed early rather than padded at the end.

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?

For a zero-required-parameter, read-only search tool with no output schema, the description supplies everything needed: valid input style, empty-input semantics, return contents, and the alternative tool for a nearby-but-different intent.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by showing the expected phrasing of `task` ('more loot on my server', 'shorter nights'), which tells an agent what granularity of natural-language query actually retrieves results.

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?

States a specific verb and resource ('Find the dzpage.com browser tool') and anchors it with four concrete example tasks that make the input domain unambiguous. It also names the sibling where_to_find_item as the tool for a different question, which is exactly the differentiation an agent needs.

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?

Explicit when-to-use ('a task described in plain words'), explicit degenerate case ('With an empty task it lists all tools'), and explicit routing away ('To answer where a specific item spawns, call where_to_find_item instead'). Nothing about selection is left to inference.

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