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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral contract: results are ordered by party_id, pages default to 100, next_cursor is always present and null on the final page, and the call is not metered. It stops short of covering error behavior or filter edge cases.

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?

Front-loaded with purpose, then row shape, then pagination mechanics — a logical order with little filler. The row-field enumeration is somewhat long, and it partly duplicates the output schema, but it is dense rather than padded.

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 paginated list tool with full schema coverage and an output schema, the description covers what an agent needs: scope, ordering, page size, and the cursor contract. Minor gaps are the semantics of the name filter and error conditions on bad party_type values.

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 all five parameters are already documented, including the 1..200 limit bounds, cursor opacity, and the party_type enum. The description largely restates that (default 100, enum values, cursor round-trip) without adding new meaning about how the name filter matches.

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 and resource ('Lists the workspace's parties') and defines what a party actually is — 'the people, businesses, and institutions its documents name' — which removes ambiguity an agent would otherwise have. It does not explicitly contrast itself with the sibling get_party_profile, so it stops short of a 5.

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?

Usage is only implied: enumerate parties in a workspace, page through with cursor. There is no explicit statement of when to prefer this over get_party_profile for a single party, nor any precondition or exclusion beyond 'read-only and not metered'.

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