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

The description adds significant behavioral context beyond annotations: it discloses that delivery_coverage.cities may be capped, provides guidance on handling that, explains pagination with kifly:hasMore and kifly:nextCursor, and states default page size and max. Annotations are already readOnlyHint and idempotent, which are consistent.

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 front-loaded with purpose and efficiently packs details about token, return fields, city cap, and pagination. Each sentence adds value, though it could be slightly more structured for readability.

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?

Given no output schema, the description adequately covers return fields (handle, name, etc.), pagination behavior, and the city cap nuance. It fully prepares the agent for correct usage without missing critical details.

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% for both parameters, and the description adds value by explaining the cursor parameter (pagination cursor from previous response) and the default/max limit, which are not fully detailed in the schema descriptions.

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?

Clearly states the tool lists all active sellers on the Kifly network, distinguishing it from sibling tools like get_seller (which fetches details for one seller) and search_products (which searches products). The verb 'list' and resource 'active sellers' are specific.

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 says to use this tool before calling get_seller or search_products for discovery. Also mentions the requirement for a network token. Lacks explicit when-not-to-use, but the usage context is well-defined.

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