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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description reinforces this by naming the GET endpoint. It adds field-level meaning (how partyId is derived from partyUrl) but says nothing about result volume, pagination beyond the limit parameter, or whether parties are account-scoped or shared.

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 dense sentences with no filler: the returned attributes are listed first and the operational hint follows. Nothing needs to be trimmed and nothing is buried.

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?

With no output schema, the description carries the burden of describing returns and does so by listing the key row fields, and it flags the cross-tool id relationship. It is only slightly short of complete because it does not describe pagination or total-count behavior for a list endpoint with a default row cap.

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 baseline is 3, and the schema itself documents limit, fields, updated_since and updated_until including the 30-day window rule. The description earns a bump by enumerating the row attributes (partyId, name, type, roles, status), which is directly actionable when choosing values for the fields parameter.

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 (party groups) and enumerates the party subtypes (customers, suppliers, carriers), so an agent knows exactly what entity set this returns. It also names the endpoint. It stops short of explicit sibling differentiation, but no sibling tool touches parties, so the risk of confusion is low.

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 only usage guidance is the embedded workflow hint that partyId should be used as supplier_party_id when drafting a purchase order, which usefully links it to finale_create_draft_purchase_order. There is no explicit when-to-use statement, no exclusions, and no guidance on the update-window filtering.

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