ywm_get_search_urls

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

No annotations are present, and the description only indicates a read operation ('Get'). It does not disclose behavioral traits like rate limits, authentication requirements, or data freshness. The parameters document that host_id can be optional via configuration, but overall transparency 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 is a single concise sentence with no fluff, but it lacks structure and fails to include important details. It is appropriately short but under-specified for a tool with multiple parameters and many siblings.

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 tool has no output schema, so the description should explain what is returned (e.g., list of URLs with metadata). Without that, and with multiple similar siblings, the description is incomplete. The parameter descriptions help slightly, but overall the tool feels underspecified.

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 three parameters (limit, offset, host_id) have descriptions in the schema, and the tool description adds no extra meaning. With 100% schema coverage, the baseline is 3, and the description does not compensate beyond what the schema provides.

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 'Get URLs found in search' clearly states the action (get) and resource (URLs from search). However, it lacks specificity about what search refers to (e.g., search queries, search results) and does not distinguish it from sibling tools like ywm_get_search_urls_history.

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. Sibling tools such as ywm_get_search_urls_history or ywm_get_important_urls could serve similar purposes, but the description offers no context for differentiation.

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