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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds the returned field set (address, phone, email) and the getter endpoint, but says nothing about pagination defaults, page-size limits or result ordering even though max/first exist.

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?

Two compact sentences with the entity scope front-loaded and filtering second. The trailing "GET /v6/party/list" is of marginal use to an agent but costs little; nothing is padded or redundant.

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 read-only list endpoint with no output schema, the description covers what the tool returns and how to narrow it, and the annotations carry the safety profile. The remaining gap is pagination semantics (page size default, total counts, how to iterate), which an agent paging this list would want.

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 max, first, category and starts_with are all documented in the schema itself, including the enum and defaults. The description's filter sentence merely restates category and starts_with without adding format, matching behavior, or precedence rules. Baseline 3 applies.

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?

Specific verb+resource ("List parties") plus an enumeration of what a party is (customers, growers, suppliers, owners, individuals or organisations) and the fields returned. The plural "List" wording implicitly separates it from the singular vintrace_get_party, though it never names that sibling explicitly.

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?

"Filter by the start of the name and category" hints at how to narrow results, but there is no statement of when to reach for this tool versus vintrace_get_party (single lookup) or vintrace_search_items. Usage is only implied by the fact that it is a list operation.

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