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. It usefully states that seller authentication is required and "List" implies a read operation, but it does not disclose return behavior, pagination, privacy considerations, or any side effects suggested by the notification_message parameter.

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 short sentence with no wasted words. The core purpose and seller-auth constraint are front-loaded, making it easy to scan.

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 simple two-parameter list tool with full schema coverage, the description is enough to call the tool. However, with no annotations and no output schema, it still omits useful context about what "potential buyers/leads" contains, whether results are paginated, and what notification_message is for.

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 schema already documents both parameters, including that step_204_url_path_4 is an advert id from list_my_ads. The description adds only the general "YOUR goods advert" framing and does not add parameter-level detail beyond the schema.

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 gives a specific verb and resource: "List potential buyers/leads." It scopes the result to "YOUR goods advert" and notes seller authentication, which distinguishes it reasonably well from generic message or listing tools, though it does not explicitly name alternatives.

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?

The seller-auth note and advert scoping imply when the tool is applicable, and the schema says the advert id comes from list_my_ads. However, the description itself does not state when to use this versus siblings such as list_messages or list_job_applicants, nor does it provide exclusions.

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