List vendor site assignments

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing beyond that: no note on auto-pagination behavior, result volume, or authorization requirements, which are the remaining behaviors an agent would care about for a listing call.

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, front-loaded sentence with no filler. It is efficient, though the brevity is also what leaves the other dimensions thin.

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 paginated list tool with full schema coverage, no output schema, and annotations covering the safety profile, the description is minimally adequate. It stops short of describing the returned assignment record or how site_id/vendor_id filters combine, which would round it out.

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% (page, per_page, site_id, vendor_id all documented with formats and defaults), so the schema carries the parameter burden and the baseline of 3 applies. The description adds no filtering syntax or semantics beyond what the schema already states.

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 ('List') and resource ('vendor-to-site assignments') and clarifies the record's meaning as a vendor/site mapping. It is distinguishable from generic list_* siblings, but does not explicitly contrast with get_vendor_site_assignment or the related list_vendors/list_sites tools.

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 on when to use this versus alternatives such as get_vendor_site_assignment, list_vendors, or list_sites, and no indication of typical scenarios (e.g., auditing coverage). The agent must infer usage from the name alone.

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