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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not state that this is a read-only listing, that the address id must be an active address (only the schema says so), what 'featured' vs 'tagged' means, or how pagination behaves. For a tool with zero annotation coverage this is a significant gap.

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?

A single eight-word fragment with zero padding and the geographic constraint front-loaded. It is efficient, though its terseness borders on under-specification rather than genuine conciseness.

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?

With four parameters, no annotations, and no output schema, the description should explain what a caller gets back, what featured/tagged means, and how paging works. Instead it offers one clause, leaving an agent to infer nearly all calling behavior from the schema alone.

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 every parameter is already documented, and the baseline is 3. The phrase 'near a delivery address' does add a small amount of meaning by explaining the role of the required address id, but the description says nothing about pagination or the notification_message fallback that the schema documents.

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 names the resource (featured and tagged vendors) and scopes it geographically to a delivery address, which distinguishes it from siblings like search_product or search_menu_by_address. However it is a noun phrase with no verb and never explicitly says what it does with those vendors (list them) or how it differs from a vendor search.

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 when-to-use, when-not-to-use, or alternative-tool guidance appears in the description. The only usage hint in the whole definition ('Use when user asks for more vendors or next page') lives in the schema for step_40_page, not the description, and there is no mention of when to prefer this over search_menu_by_address or search_product.

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